mcpbeat

Keyboardia MCP Server

io.github.adewale/keyboardia
answering

Keyboardia is answering right now. Last checked 15 min ago. It exposes 7 tools. Last commit 2 Aug 2026.

Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
303 ms
Response time
average over 24h
3
Stars
last commit 2 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add keyboardia --transport http https://keyboardia.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "keyboardia": {
      "url": "https://keyboardia.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.keyboardia]
url = "https://keyboardia.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "keyboardia": {
      "url": "https://keyboardia.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "keyboardia": {
      "url": "https://keyboardia.dev/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

session
create_session
Create a new editable Keyboardia session with the normal defaults and return its shareable URL. The session starts with no tracks; use edit_session to add them. Pass the same idempotency_key when retrying so an uncertain attempt cannot leave duplicate sessions behind.
get_session
Read the current tempo and compact track patterns from an existing Keyboardia session.
analyze
analyze_session
Describe what is happening musically in a session — rhythm, pitch content, inferred key, and chords — without changing anything. Use this to explain music rather than to edit it. Results come from the same music-theory module the browser's Key Assistant and Chromatic Grid use, and report where the analysis is uncertain instead of guessing.
edit
edit_session
Make one narrow, retry-safe edit to an existing collaborative session. After every attempt, the next Keyboardia call must be get_session for the same session. A successful call includes a backwards-compatible compact snapshot plus an acknowledgement. That snapshot is not authoritative verification; do not make another edit or finish from it. Read with get_session next. Supported operations: add_track, set_track_instrument, set_steps, and set_tempo. set_steps changes only the named steps; it never replaces a track or session. set_track_instrument replaces only a track's sound source, keeping its pattern, mix, timing, and custom name.
export
export_midi
Export the session as a base64-encoded Standard MIDI File, matching what Keyboardia's own Export MIDI produces for the same music. The session is not modified. The result lists any session features a MIDI file cannot carry rather than approximating them silently.
publish
publish_session
Freeze the current music into a new immutable session and return its URL. The source session stays editable at its own URL. Only call this when someone explicitly asks to publish; it is never a side effect of editing or exporting.
remix
remix_session
Copy an existing session — published or editable — into a new editable session that records the original as its source. The source is never modified, so this is how to continue from published work.

Endpoints

URLTransportStateLatencyChecked
https://keyboardia.dev/mcp streamable-http answering 475 ms 15 min ago

Keyboardia — questions

Answers built from our own checks of this server.

What can Keyboardia do?
It exposes 7 tools, read directly from the server on our last check. Among them: analyze_session, create_session, edit_session, export_midi, get_session, publish_session and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Keyboardia working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 303 ms. The bar chart above shows every period we have measured.
How do I connect Keyboardia?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Keyboardia need an API key?
No. Keyboardia completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Keyboardia?
It answers our handshake in 303 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Keyboardia open source?
Yes — it is published under the MIT licence, written in TypeScript, 3 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.