Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

MCP Docs live preview
All projects

MCP Docs

Write down an MCP tool's contract before you call it.

MCP tool contracts lived in source code and READMEs, with no quick place to note what each tool accepts and returns.

Tech Domain · Book Dev|Published|Evidence: Prototype|Next.js, TypeScript

A public prototype demonstrates the interaction; scope and data are intentionally limited.

Case Study

Before

MCP tool schemas and usage notes were buried in source code and READMEs.

After

Tool register on the App shell: lifecycle lists with counts, search, an in-place composer and undoable removal for a small local list of MCP tools; it does not generate docs from schemas.

How it's solved

Built a client-side register to add, search, filter by lifecycle (Draft, Active, Done) and remove tool records with Undo, saved in this browser's localStorage. A read-only /api/mcp route serves short authored protocol notes and examples.

Trade-offs

Records stay in this browser only; there is no shared registry, MDX or schema import.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev