MidiPilot AI Tools Reference
In Agent mode the model does its work through tools: it inspects the file, writes events, and checks the result by calling them one after another. This page lists every tool with what it does, and points at the MCP server that hands the same set to external AI clients.
AI Tools Reference
In Agent mode, the AI has access to 27 tools (22 core + 5 FFXIV-specific) for inspecting and modifying MIDI files. The 22 core tools are the same ones exposed over the MCP server, which adds two document tools of its own:
| Tool | Description |
|---|---|
get_editor_state | Read file info, tracks, tempo, time signature, cursor position, and the selected-event count |
get_track_info | Get detailed info for a specific track: name, assigned channel, total event count, and how many of those are notes |
get_selection | Read the user's current selection as full events, each with a 0-based index (the index delete_events_by_index expects) |
create_track | Create a new MIDI track |
rename_track | Rename an existing track |
set_channel | Set the MIDI channel for a track |
remove_track | Delete a track and all its events (cannot remove the file's last track) |
insert_events | Add new MIDI events (notes, control changes, etc.) |
replace_events | Modify existing events in a range |
delete_events | Delete events in a tick range on a track |
delete_events_by_index | Delete specific events from the current selection by 0-based index (e.g. every second selected note) |
query_events | Read events in a tick range on a track |
move_events_to_track | Move events between tracks |
transpose_events | Transpose notes by semitones - a track, a tick range, or the whole file - as one undo step, optionally folded octave-wise into the bard range C3-C6 |
split_chords_to_tracks | Split a track's chords voice-wise onto new tracks (voice 1 = highest note) - the standard way to turn a chordal part into monophonic FFXIV performers |
copy_events_to_track | Copy notes to another track, optionally restricted to a tick range - e.g. double a melody onto a second performer, then transpose the copy |
search_help | Search the built-in manual - for questions about the editor itself ("how do I split drums?"), the AI looks the answer up instead of guessing |
get_help_section | Read one manual section's full text; the answer cites the page so you can click through |
set_tempo | Change the tempo (BPM) |
set_time_signature | Change the time signature |
convert_tempo_preserve_duration | Re-tempo material while keeping its real-time duration - scales event ticks and updates the tempo map so e.g. a 90 BPM vocal line fits a 180 BPM project with the bars lining up again. Works on the whole file, chosen tracks or channels, or the current selection; defaults to a dry run and requires the user's confirmation before the real pass |
set_ffxiv_mode | Turn FFXIV Bard Performance mode on or off - the five FFXIV tools below appear and disappear with it, and get_editor_state reports the current state as ffxivMode |
setup_channel_pattern | Auto-configure MidiBard2 channel mapping (FFXIV) |
convert_drums_ffxiv | Convert GM drum kit to FFXIV-compatible tone-mapped notes |
validate_ffxiv | Check FFXIV Bard Performance rule compliance: every same-tick note collision and stacked duplicate with its tick, notes outside C3-C6, and track names matching no FFXIV instrument - the same engine as Tools → Check FFXIV Playability, see Check FFXIV Playability |
analyze_voice_load | Read-only audit of the FFXIV 16-voice ceiling and 14 notes/sec/channel rate cap. Returns globalPeak, overflowRanges and rateHotspots - see FFXIV Voice Limiter |
auto_fit_voice_load | The matching action tool: thins overloaded moments and over-dense passages (whole file or a tick range). Defaults to a dry run and requires the user's confirmation before the real pass - see Auto-Fit Voice Load |
MCP Server - External AI Clients
MidiEditor AI includes a built-in MCP (Model Context Protocol) server that exposes the same 22 core tools MidiPilot uses, plus two document tools of its own - and the five FFXIV tools whenever FFXIV mode is on. Instead of using the built-in chat panel, you can connect Claude Desktop, VS Code Copilot, Cursor, Windsurf, or any other MCP-compatible client and let it edit your MIDI files directly.
Enable the MCP server in Settings → MidiPilot AI → MCP Server, copy the config JSON, paste it into your AI client, and you’re ready. All tool calls appear in the Protocol panel with the client name (e.g. “MidiPilotMCP (VS Code Copilot Claude Opus 4.6)”) and support full undo.
📖 Full MCP Server Documentation →
See also
- MidiPilot - Your AI Copilot - the overview: key features, getting started, the chat panel, and the mode comparison table.
- MidiPilot Modes and Conversations - Agent mode, the loop that calls these tools one after another.
- MidiPilot in FFXIV Bard Mode - the mode that adds the five FFXIV tools to the list.
- MidiPilot Settings and Providers - picking a model that supports tool calling, and the step limit for a run.