mcp-koii

Provides an MCP (Model Context Protocol) server that controls a Teenage Engineering EP-133 K.O. II sampler via MIDI, exposing commands for connecting to MIDI ports, playing notes and drum patterns, and browsing the device’s sound/pad mappings.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ Ai Ml mcp model-context-protocol midi music-controller teenage-engineering python automation

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

No authentication/security controls are described; the MCP server appears local and interacts with a physical MIDI device. TLS is not applicable/unspecified for local MIDI control. Dependency hygiene cannot be verified from the provided README (not enough data on versions/CVEs). Avoid exposing the server on a network interface without external protections.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a local, developer-run MCP bridge between a language model and a physical EP-133 device over USB/MIDI, and you’re comfortable running a Python process.

Avoid When

You cannot control the runtime environment (USB/MIDI access) or require strong auth/rate limiting for remote/public deployment.

Use Cases

• Control an EP-133 K.O. II using natural-language via an MCP-capable client (e.g., Claude Desktop)
• Trigger specific sounds/pads by note number, pad label, or sound name
• Generate and play drum patterns from a text-based 16th-note grid syntax
• Explore available EP-133 sound categories and the default pad configuration

Not For

• Production-grade, network-exposed services requiring hardened security and authentication
• Use cases needing cloud-hosted APIs, multi-tenant access, or guaranteed delivery semantics beyond local MIDI playback

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: None/Local runtime (implied) MCP SDK/host authentication not specified

OAuth: No Scopes: No

The README does not describe any auth mechanism for the MCP server itself; access likely depends on how the MCP host exposes/starts the process locally.

Pricing

Free tier: No

Requires CC: No

Open-source library; no pricing details provided.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Playback timing/BPM can affect whether multiple simultaneous instruments are processed (README notes higher BPM may be needed).
⚠ MIDI port discovery depends on correct device connection and MIDI mode.
⚠ Name matching for instruments/sounds likely requires exact strings (README mentions exact instrument names in quotes).

Alternatives

Use mido (or a DAW) directly to trigger EP-133 sounds without MCP A custom MIDI controller/script with a REST UI Other MCP MIDI/music device controller projects (if available)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-koii.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.