← Moose Tracker MCP

Moose Tracker MCP reference

The details behind Moose Tracker MCP: tools, analysis, formats and limits. Install ↓

Moose Tracker MCP lets an AI assistant work in Moose Tracker. The assistant writes a song as notes in MTL, a short text format. Moose Tracker checks the song, plays it on its own synth and sampled instruments, and returns audio files or a link that opens the song in the browser editor.

It is not an AI music model. Nothing on the server writes or composes music. What you get back is a normal Moose Tracker song: you can open it, change any note and keep working on it.

What a song looks like

This is a complete MTL song: a looping chiptune theme with a lead, a bass, an arpeggio and drums. bass(…) and arp(…) are chord macros, and the | in the order line marks where the loop starts.

song "Pixel Run" bpm 140 spd 6 ch 6 master 80 loop on
style chip
i1 @lead
i2 @bass
i3 @arp
i4 @drums
P A 32 /2
 1 i1 v50: A4 . C5 . E5 . C5 . F4 . A4 . C5 . A4 .
 2 i2 v56: bass(Am F x8 root o2)
 3 i3 v36: arp(Am F x8 up o4)
 d kick: x... x... x... x...
 d snare: ....x.......x...
 d hat: euclid(8,16)
P B 32 /2 = A
 1 i1 v50: C5 . E5 . G5 . E5 . G5 . A5 . G5 . E5 .
order A | A B A B

A song this size is under half a kilobyte of text. The assistant sends text, not audio, so a round trip costs few tokens.

From idea to file

  1. Research: research_composition returns advice for every stage of the song, with ranges, for the style you name. It draws on a curated library covering about 50 styles.
  2. Plan: song with a plan (sections, bars, energy) returns a skeleton with timing.
  3. Write and check: after each edit, a light analysis reports errors with line numbers, the real length and a score with fixes. It plays nothing and costs nothing.
  4. Deep analysis, once or twice near the end: an analysis-only render that measures loudness per section and flags mix problems.
  5. Listen or export: a share link plays the song in the browser with no render. render makes files for a game, app or video.

The eight tools

ToolWhat it does
describeA short index, then topics on request: the MTL grammar, presets, sample packs, instrument templates, example songs, limits and error messages.
sfx1 to 16 sound effects per call as WAV files, from 28 recipes (coin, jump, laser, explosion and more) or from your own notes. For app UI sounds, give each sound a role (press, release, toggle, success, warning). Results carry playback hints: cooldown, maximum overlap and gain.
research_compositionComposition advice from the curated library, found with a semantic search index. It returns advice only, never notes or audio.
songPlans, checks, edits and analyzes a song. Batch edits (add, replace or remove lines, change instruments, mix and order) come back as the edited song, with a share link.
renderAudio files: WAV, Ogg Vorbis or Opus, with loops, cues, stems and adaptive game-music kits (below).
convertMoves a song between MTL, a .mtk project file, a share link, MIDI and MOD, XM, S3M or IT tracker modules, in either direction.
assetsFresh download links for files already rendered, with an optional sha256 check.
feedbackSends a bug report or suggestion to us, with an optional song attached.

Analysis and mix flags

Every song and render reply carries a score check: a score from 0 to 100, the key, the sections, the energy curve and up to five issues, each with a fix. The rules are fixed and deterministic, with no AI involved. Name a genre from the list of 99 and the score uses that genre's profile, so a lo-fi loop isn't judged like a rock anthem. An unknown genre is refused, with the nearest valid names, rather than guessed.

A deep analysis adds measured loudness and peak per section, plus mix flags that name the track, the bar and the change to make. Some examples:

FlagMeaning
MIX.BURIEDA part sits far under the loudest one, or can't be heard at all.
MIX.LOWMASKThe bass covers the kick drum.
MIX.SUBLOWA synth part plays mostly below 40 Hz, where it sounds like rumble rather than notes.
MIX.SAMPLEFLATA sampled part plays every note at one velocity, so it plays the same recording every time.
MIX.KITKEYDrum notes fall on keys the sampled kit doesn't map.
MIX.PEAKThe true peak is too hot, or samples clipped.
PIERCEA bright, high tone is held or repeated long enough to be uncomfortable to hear.

A choice made on purpose can be marked as kept (for example, a deliberately buried texture). Later replies list it under "Kept on purpose" instead of flagging it again.

Files and formats

Rendered files are deleted after about 2 hours, so download what you want to keep. Share links (moosetracker.app/s/…) are encrypted so we can't read them, and expire after 90 days.

Adaptive game music

Write one song, export it as layers your game mixes live, calm to full intensity, with stingers, a manifest and setup notes for Godot, Unity, FMOD and Wwise.

render with adaptive:true returns one zip with a looping file per role (pad, bass, drums, arp, lead). Every layer is exactly the same length, down to the sample, so the layers stay in time when the game starts them together. Intensities group the layers, each one adding to the one before: by default calm (pad and bass), tense (adding drums and arp) and full (everything). adaptive.levels names your own, such as explore and fight. The game moves between intensities by fading layer volumes.

With cues, the first cue becomes the layers and each further cue becomes a one-shot stinger. A song with an Explore loop and a Win cue, rendered with

render({ mtl, adaptive: true, cues: ["Explore", "Win"] })

returns five layers grouped into calm, tense and full, a Win stinger, and three more files:

The player card

In clients that support MCP Apps, an open standard for interactive results, render and sfx results appear as a small player in the chat. It has play and pause, a waveform you click to seek, loop, and an A/B switch against the previous render of the same song. It also lists the song's sections and instruments and has a button to open the song in Moose Tracker. Clients without MCP Apps get the same text and links.

Chords, sub-channels and sounds

Each channel can split into up to 16 sub-channels, so a piano, harp or guitar part can let notes ring over each other. The assistant can send a part as a plain list of notes (pitch, start beat, length and velocity). Moose Tracker places each note on a free sub-channel with the same allocator the piano roll uses, and the reply says where each note landed. Arpeggios can cut (each note stops the one before) or ring (each chord tone on its own sub-channel).

Each part can use the synth or a sampled instrument. The sample library has pianos, basses, strings, brass, reeds, woodwinds, guitars, mallets, organs, voice and drum kits, all CC0 except the TR-808 kit, which its author released as "absolutely free". In sampled kits each drum sits on its General MIDI key (C2 kick, D2 snare, F#2 closed hi-hat). Velocity picks among a pack's recorded layers, so a soft note plays a softly played recording. The synth has presets by role and lets the assistant design a new voice and hear it in about a second.

Install

Server address, using Streamable HTTP with no sign-in and no API key:

https://mcp.moosetracker.app/mcp

Add it as a remote MCP server in your client and choose no authentication if the client asks.

If your client can only start a local command, use the moosetracker-mcp package. It forwards to the same server and holds no engine code and no secrets:

{
  "mcpServers": {
    "moose-tracker": { "command": "npx", "args": ["-y", "moosetracker-mcp"] }
  }
}

Steps for specific clients, plugin packages with checksums and copy-paste instructions are on Use Moose Tracker with your AI.

After a Moose Tracker update, the server changes in place, but a client keeps the tool list it fetched when it connected. Refresh or reconnect the server in your client, or start a new conversation, to load the new list.

Limits and terms

Moose Tracker MCP is free to use with fair-use limits. describe(topic="limits") lists the current numbers. Use of the server is covered by the API & MCP terms and Privacy. The Content license covers the sounds and demo songs.


Contact: moose@moosetracker.app.

© 2026 Kurtis Alexander. All rights reserved. Moose Tracker™ and the moose logo are unregistered trademarks of Kurtis Alexander.