The workspace is also an MCP server, the standard way of handing tools to an AI agent. Once an agent is connected, it can turn a scanned page or a MIDI file into sheet music, in the middle of whatever else it is doing. It spends credits as the workspace does.
connect
- On the integrations page, choose your agent and copy the line it gives. For Claude Code it is one
claude mcp addcommand. The first time, it opens your browser so you can sign in to your account and allow it. Without an account, that page gives a line for/api/v1/mcp/guestinstead. It reads sheet music, with a guest's few credits counted by your address. - Ask the agent for what you want in plain words: “turn sonata.pdf into sheet music with kobimusic”.
- The agent uploads the file with a curl command the server gives it, asks for the conversion, and downloads what comes back. Files never travel through the model itself.
what the agent is given
| tool | what it does |
|---|---|
| create_upload | answers with the curl command that uploads a local file, and the handle to refer to it by |
| sheet_to_score, find_beats, beat_align, dehumanize, midi_to_sheet | one conversion: a file in (a handle, or a path under /demos), a link to the result out |
| fit_to_beats | a MIDI file and a beat map in, each by name (midi, beats), the MIDI re-timed onto the beats out |
| list_nodes, list_files | the kinds of node a flow is made of; your files (with the files permission), the site's demos and built-in automations |
| get_file, put_file | a link to one of your files; an upload saved into your files (both need the files permission) |
| validate_flow, run_flow, get_run | check a flow; run it, which waits for the answer a while and then hands back a run to ask after; ask after a run that is still going |
Upload handles and result links last a quarter of an hour, so an agent that comes back later uploads again.
many files
An agent can go through a folder of files, one call for each. Calls from one person go 2 at a time at most, and the links last a quarter of an hour, so have it download each result as it arrives. For a whole collection, read for institutions.
signing in
An agent signs in through the browser with OAuth, and the app shows up under integrations on the settings page, where you can disconnect it. A key or an app can use the tools as you. If you allow it, it can also see and change your files, with list_files, get_file, put_file and flows that save. It can never change your account.
protocol versions
The endpoint speaks the current MCP revision (2026-07-28, which has no handshake) and the three before it, which open with initialize. There is nothing to configure: it answers each client in the version it speaks.