SP6 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Offline tools for planning Kurzweil SP6 Multis (unofficial; no MIDI, no device access). Typical flow: sp6_capabilities -> sp6_file_inspect (find template + empty IDs) -> sp6_multi_read (template) -> sp6_multi_validate (sheet) -> sp6_multi_build -> tell the user how to send ONLY that Multi from the editor. Never claim anything was sent or saved. Notes use C4 = MIDI 60. Omit fields you cannot write; they keep the template value.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sp6_capabilitiesB | What this server can and cannot do: file formats, writable Multi fields with evidence, device support. |
| sp6_spec_schemaA | JSON Schema of the setting sheet accepted by sp6_multi_validate / sp6_multi_build. |
| sp6_file_inspectC | Hash, inventory and a paged object list of a .ksp6/.fmlt file. path is relative to the work root or absolute. Empty records in a file do NOT prove the keyboard slot is empty. |
| sp6_object_findA | Find Programs or Multis whose name contains query (case-insensitive) in a file. Use this to turn names such as "Prophet Pad" into IDs. Names come only from the given file; factory names are not bundled with this server. |
| sp6_multi_readB | Decode one Multi: name and per-zone enabled/channel/program/keys/transpose (+ read-only volume/pan). |
| sp6_multi_validateB | Check a setting sheet against its template file and report every problem at once. Returns valid / can_build, errors and warnings with field paths, the effective zones (sheet over template) and sounding note ranges. |
| sp6_multi_buildA | Write a NEW Multi file inside the artifacts directory. Never touches the template or the keyboard. output_path is relative to the artifacts directory, must not exist and must end with .ksp6 or .fmlt matching output_format. 'ksp6' (default) is a complete copy of the template bank with the new Multi in one empty record; 'fmlt' follows the editor layout (Multi, then each zone's Program with its FX/algorithm records); user Programs are left out and flagged PARTIAL_EXPORT. |
| sp6_artifact_diffC | Compare a template/source file with a generated file (records and decoded Multi fields). artifact_path may be relative to the artifacts directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: file-level inspection (hash/inventory), name-to-ID lookup, single-Multi decode, validation, build, and diff. The three file-touching tools (sp6_file_inspect, sp6_object_find, sp6_multi_read) could be momentarily confused since they all read file contents, but descriptions clearly delineate file-level vs. name-search vs. single-object decode.
All tools share the sp6_ prefix and mostly follow a consistent resource_action pattern (sp6_file_inspect, sp6_object_find, sp6_multi_read, sp6_multi_validate, sp6_multi_build, sp6_artifact_diff). Minor deviations: sp6_spec_schema and sp6_capabilities are noun-only without an action verb, but overall highly predictable.
Eight tools is well-scoped for a domain-specific file manipulation server (schema, capabilities, inspect, find, read, validate, build, diff). Each tool earns its place with no redundant or filler tools.
The surface covers the full workflow of inspect -> find -> read -> validate -> build -> diff, which is a coherent lifecycle for editing Multi files. Gaps remain: there is no update or delete of an existing Multi in place (build only creates new files), and no direct write-back, though the safety-by-design approach is workable.