MCP Tools Lab
Standalone MCP-shaped tool server exposing experiment catalog search over a local registry snapshot.
Run this experiment yourself
Demos are not embedded on this site. Deploy a standalone copy on Vercel or run the experiment app locally.
Local development
cd apps/experiments/mcp-tools-lab pnpm install pnpm dev
Then open http://localhost:3010.
This is an experimental demo. Use it as a starting point for your own projects.
A standalone MCP-shaped tools endpoint that searches a local experiment catalog snapshot. The hub MCP at apps/docs/app/api/mcp indexes docs via fumadocs; this lab focuses on catalog tools you can deploy alone.
Features
- tools/list and tools/call RPC shape
- search_experiments / get_experiment / list_experiments
- Local registry snapshot in logic.ts
- Interactive demo UI
API Reference
GET /api/mcp
Server info + tool schemas.
POST /api/mcp
{ method: "tools/list" | "tools/call" | "initialize", params? }.
Implementation Details
Catalog search is pure (searchCatalog, getBySlug). The route validates RPC bodies with Zod.
Use Cases
- Agent tool servers
- Catalog search for AI clients
- Teaching MCP tool shapes
Limitations
- Not the full MCP transport stack of the docs hub.
- Snapshot may lag the live registry.
- No auth on the demo endpoint.
Use in your project
Deploy or copy apps/experiments/mcp-tools-lab/ and adapt the Route Handlers and pure helpers in logic.ts. Keep honest fallbacks when optional services are missing.
Deployment
Local Development
cd apps/experiments/mcp-tools-lab
pnpm install
pnpm devConfiguration
| Variable | Required | Purpose |
|---|---|---|
| (none) | - | Works without extra secrets |
Vercel / Next.js Features Used
- Route Handlers
- MCP-shaped tools
Next Steps
- Explore related labs from the registry
relatedSlugs - Harden secrets, auth, and input limits before production
- Prefer platform primitives when you outgrow demo patterns