mcp-lab
ridzkyyy/mcp-lab
Postman for MCP servers — connect, explore, and test any Model Context Protocol server from your browser.
Instalação
npx convez-ai ridzkyyy/mcp-lab1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
🧪 MCP Lab
Postman for MCP servers — connect, explore, and test any Model Context Protocol server from your browser.

▶ Live demo · Quickstart · Roadmap
What is this?
MCP servers expose tools, resources, and prompts to AI agents — but testing one today means wiring it into a client or squinting at raw JSON-RPC. MCP Lab is a clean web UI that lets you point at any MCP server and actually use it: list its tools, fill in arguments through a generated form, fire a call, and read the result formatted — not as a wall of JSON.
Think Postman, but speaking MCP instead of HTTP.
Why you'd want it
- 🔌 Connect in seconds — paste an MCP server URL (HTTP / SSE / Streamable HTTP), no install
- 🧰 Explore everything — tools, resources, and prompts in one panel
- 📝 Typed argument forms — auto-generated from each tool's input schema, with validation
- 📦 Save & share collections — keep your common calls, share a link with a teammate
- 🌗 Designed, not default — readable result rendering, light/dark, keyboard-first
Quickstart
git clone https://github.com/ridzkyyy/mcp-lab.git
cd mcp-lab
npm install
npm run dev
Open http://localhost:5173, paste an MCP server endpoint, and start calling tools.
Trying it out? Spin up any HTTP-transport MCP server (or use the bundled example endpoint) and connect. Want something meatier? fleet-mcp serves a live simulated GPS fleet — trucks, geofences, NMEA. Paste
https://fleet-mcp.vercel.app/mcpinto the connect bar and go.
How it works
Browser (MCP Lab) ──HTTP/SSE──▶ MCP server ──▶ tools · resources · prompts
▲ │
└───────────── formatted results ◀──────────────────┘
MCP Lab talks the MCP protocol directly over HTTP-based transports. (stdio servers need a local bridge — that's on the roadmap.)
Roadmap
- Connect to HTTP / SSE MCP servers
- List & invoke tools with schema-generated forms
- Resources & prompts panels
- Save / export / share request collections
- stdio transport via local bridge
- Auth presets (headers, bearer tokens)
- Request history & diffing
Contributing
Issues and PRs welcome — especially transport adapters, schema-form edge cases, and result renderers.