An AI assistant like Claude can compose and edit game music in Mowjera through its MCP server: you connect your own AI client with a personal access token, then ask for music in plain language. The assistant writes notes, builds game states and checks the result by calling Mowjera's tools. It works as a co-composer that you direct, not as a one-click album generator.
Last reviewed: October 2026
What is MCP, in two sentences?
The Model Context Protocol (MCP) is an open standard that lets an AI assistant call tools and read resources provided by another application. In practice, the app exposes a list of actions with descriptions, and the assistant decides which to call to carry out your request.
What can an AI client do in Mowjera?
Mowjera's MCP server exposes many tools, grouped by job. The exact list evolves, so ask your assistant to list the tools it can see. At a category level:
| Category | What it covers |
|---|---|
| Scores and state | List, view, create and duplicate scores; add, update, reorder and remove game states and transitions |
| Track and note editing | Add and configure tracks, write, replace, transform and remove notes, set automation and master settings |
| Composing helpers | Suggest chord progressions, write chords and drums, develop a motif, apply feel (humanize, swing), orchestrate, plan a form |
| Analysis | check_music and analyze_harmony read the notes; analyze_mix measures loudness, spectral balance and masking |
| Sound design | List instruments, apply mix and master presets, create procedural SFX and ambience tracks |
| Render and export | Render audio, export MIDI, MusicXML, WAV, FLAC, OGG and a game-engine bundle |
| Safety | Version history and restore; every AI session saves a restore point first |
There are also workflow prompts for jobs such as an adaptive game score, a film cue, a remix, mix and mastering. The assistant also reads built-in style guides, so it can follow genre conventions such as fantasy RPG or dark ambient.
What are the honest limits?
Setting expectations matters more than hype.
- Your own AI client does the writing. Mowjera does not generate the music for you through MCP. Your assistant (Claude Code, Claude Desktop, Cursor or another client) reasons about it and calls the tools.
- It is a paid-plan perk. MCP access is included with Composer Pro ($12 per month) and Studio ($49 per month), not Free. The check runs on every request.
- Claude cannot hear. It works from the notes and from measurements. Audio rendering and analysis, such as
analyze_mix, need an editor tab open in your browser, because the audio engine runs there. Your ears make the final call. - Sound quality depends on the instruments. Built-in voices are good for sketching and many releases, but they are not a top-tier orchestral library. You can export MIDI or MusicXML and finish elsewhere.
- Stage-by-stage works best. One prompt for a finished album gives weak results. Feedback at each check-in gives strong ones.
How do you set it up?
- Create a token. In your dashboard, open the AI assistant access (MCP) card and create a token. Use read scope to inspect and analyse, and write scope if the assistant should edit. The token is shown once, so store it like a password.
- Connect your client. For Claude Code, the documented command is:
claude mcp add --transport http scoreforge https://your-site.example/api/mcp \
--header "Authorization: Bearer sf_pat_XXXXXXXX"Replace the URL with your Mowjera address. Claude Desktop connects through a small mcp-remote bridge in its config file, and Cursor takes a URL and header in its mcp.json. 3. Open the score in the editor. Keeping a tab open lets edits appear live, and enables rendering and analysis. 4. Ask. Start with a brief rather than a command.
What does a realistic prompt-to-result session look like?
Suppose you are making a small platformer and say:
Make a three-state score for a forest platformer: calm exploration, tense chase, and a short victory. Bright acoustic palette, 110 BPM, loops that cross-fade cleanly.
A good session typically goes like this:
- Plan. The assistant proposes a key, tempo, form with bar counts and instrument palette, and waits for your OK.
- Build. It creates the score, adds the three states, and writes chords, bass, melody and drums for each, reusing the same motif so the states feel related.
- Check. It runs
check_musicandanalyze_harmonyto catch range problems, clashing notes or weak voice leading. - Listen. With your editor open, it plays the music and asks specific questions, such as whether the chase feels urgent enough.
- Revise. You say "the chase melody is too busy at bar 12". It edits only that.
- Mix and deliver. It runs
analyze_mix, applies a preset, and exports a game bundle for your engine.
Every edit can be undone with Ctrl+Z in the editor or restored from version history, so experiments are cheap. For the underlying music design, see adaptive music 101 and how AI composes game music.
Why use MCP rather than a chat window?
A chat model alone can describe a melody in text. With MCP it can place the notes in a real score, hear measured results, and keep the file consistent across dozens of edits. The structure also reduces mistakes: inputs are validated, sizes are capped, and errors come back as readable messages the assistant can fix.
It is also a good fit for tedious jobs: transposing every state, tightening drum fills, or creating five loop variations to compare. For a broader view of how the file ends up in your project, see the Godot tutorial.
Should you try it?
If you already use an AI coding assistant and have a game to score, a short experiment is cheap. A Composer Pro plan includes MCP access; you can start with the free plan to learn the editor first and upgrade when you want the assistant connected. Keep your expectations realistic: treat it as a fast sketching partner, and review every result with your own ears.
FAQ
What is the Mowjera MCP server?
It is an endpoint that lets an AI client such as Claude Code, Claude Desktop or Cursor read and edit your Mowjera scores through tools. You authenticate with a personal access token. The assistant can then add states and tracks, write notes, run checks and export audio on your behalf.
Does Mowjera write the music for me?
No. With MCP, your own AI client does the composing, and Mowjera provides the tools, instruments and style guidance it works with. Quality depends on your brief, your feedback and the assistant you use. Treat the result as a collaborative draft that you refine.
Which plans include MCP access?
MCP access is part of the paid plans, Composer Pro at $12 per month and Studio at $49 per month. The Free plan does not include it. The plan is checked on every request, so the assistant stops working if you downgrade, and resumes if you upgrade again.
Can the AI hear the music it writes?
Not directly. It reasons from notes and from measurements such as loudness and spectral balance, which require an open editor tab because audio rendering happens in the browser. It can play the music for you and ask questions, but you are the one who listens.
Is it safe to let an AI edit my score?
The design limits the risk. Every AI session saves a restore point before its first edit, edits are undoable in the editor, and version history lets you restore an earlier state. Read-only tokens can inspect and analyse but not change anything. Publishing and pricing changes happen only when you explicitly ask.