PlayByKey Music Theory
PlayByKey Music Theory is an MCP server published by playbykey.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does PlayByKey Music Theory support the current MCP specification (2026-07-28)?
Not yet confirmed. PlayByKey Music Theory is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is PlayByKey Music Theory a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for PlayByKey Music Theory (as of 2026-08-20).
How do I connect to PlayByKey Music Theory?
PlayByKey Music Theory is available via the package npm:@playbykey/theory-mcp, the official MCP Registry under com.playbykey/theory-mcp, the source repository at https://github.com/digitalbrewllc/playbykey-dev-tools. Authentication: unknown. Transports: stdio.
Does PlayByKey Music Theory support MCP revision 2025-11-25?
Yes. PlayByKey Music Theory supports MCP revision 2025-11-25 (checked 2026-08-20).
Does PlayByKey Music Theory support MCP revision 2026-07-28?
No. PlayByKey Music Theory was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were PlayByKey Music Theory's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Chords, scales, progressions, transposition, and MIDI tools for music theory AI agents.
Which MCP spec revisions does PlayByKey Music Theory support?
PlayByKey Music Theory has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is PlayByKey Music Theory?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for PlayByKey Music Theory
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 0
- Last pushed
- (61 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: developer-tools, music-notation, music-programming, music-theory — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
2.0.1- Last published
- First published
- Releases
- 13
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 633 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for com.playbykey/theory-mcp at version 1.6.0 - lists package npm:@playbykey/theory-mcp and repository https://github.com/digitalbrewllc/playbykey-dev-tools - accessed
- npm registry metadata for @playbykey/theory-mcp at published version 2.0.1, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed