mcpplay
The FastAPI /docs experience, for MCP servers.
Documentation • Getting Started • Issues
mcpplay gives you a browser-based playground for any MCP server. One command, and you get auto-generated forms, live results, and a full execution timeline.
Installation
pip install mcpplay
mcpplay demo
Your browser opens to http://localhost:8321. That's it!
Point it at your own server
mcpplay run server.py
mcpplay run --command "node server.js"
mcpplay run --command "uvx my-mcp-server"
Options
mcpplay run server.py --port 9000 # Custom port (default: 8321)
mcpplay run server.py --no-open # Don't auto-open browser
mcpplay run server.py --no-reload # Disable hot reload
mcpplay run server.py --env API_KEY=xxx # Pass env vars to server
Features
- Schema-aware forms - auto-generated from your tool's JSON Schema, with enums, nested objects, arrays, and defaults.
- Live execution - run tools and see structured results instantly.
- Persistent timeline - every call logged with inputs, outputs, and latency. Replay with one click.
- Hot reload - edit your server, mcpplay restarts it. Session and timeline preserved.
- Localhost-only - bound to
127.0.0.1with Origin validation. No remote exposure.
How It Works
Browser UI ←→ mcpplay (Python proxy) ←→ Your MCP Server
(Svelte) (uvicorn + WebSocket) (stdio)
mcpplay spawns your server as a child process, connects via stdio, and proxies everything through a WebSocket to the browser. Executions are logged to a local SQLite database.
Comparison
| mcpplay | MCP Inspector | MCPJam Inspector | |
|---|---|---|---|
| Install | pip install |
npx (Node required) |
Docker |
| Python native | ✅ | ❌ | ❌ |
| Form generation | Full JSON Schema | Basic inputs | Basic inputs |
| Hot reload | ✅ | ❌ | ❌ |
| Execution timeline | Persistent, replayable | Log | Log |
Development
git clone https://github.com/gauthierpiarrette/mcpplay
cd mcpplay
# Python backend
uv sync --dev
uv run pytest
# Frontend (Svelte)
cd frontend
npm install
npm run dev # Dev server with HMR
npm run build # Build to src/mcpplay/static/
License
Apache 2.0
Metadata
Release files for mcpplay 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcpplay-0.1.0.tar.gz | 469.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcpplay-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 553.3 kB
Release files / mcpplay-0.1.0.tar.gz
| Download URL | mcpplay-0.1.0.tar.gz |
|---|---|
| Size | 469.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4cbe9ddcb5742be1abe0d689fee58e5d001f30e6197bc2eba497f878e3c06a1b
|
|
BLAKE2b-256 checksum How to use checksums |
e7461a5af75cb8b8552644a6130092a753f32f5f2c811da33c09f89a693131f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 18, 2026.
Transparency logRelease files / mcpplay-0.1.0-py3-none-any.whl
| Download URL | mcpplay-0.1.0-py3-none-any.whl |
|---|---|
| Size | 83.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f44b3c8dafdb459591cc03c7ec11a7d989a5efa2d473ba8b03c5089e45ad4f6
|
|
BLAKE2b-256 checksum How to use checksums |
bd937b63b6b4bc5c834ffac66e0caf4d77cbf823295d785252dfd69ab5634a32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 18, 2026.
Transparency log