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.
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
The Solopreneur Tech Stack: Tools and Systems for One-Person Operations
A deep dive into the tools, automations, and systems I use to run 100+ projects as a solo operator — from MCP servers and AI agents to deployment pipelines and analytics.
Building 100 Micro-Frontends: Lessons from a Solopreneur Journey
How I built and deployed 100 independently deployed micro-frontends on Vercel, the architecture decisions, trade-offs, and what I learned about scaling a one-person dev operation.
AI Integration Patterns for Web Developers: A Practical Guide
Practical patterns for integrating AI into web applications — from prompt engineering and streaming responses to building AI-powered tools that solve real user problems.
Related Projects
More in Tech Domain · Book Dev
Book Reviews
Book review archive with ratings, categories and key takeaways
Notes App
Single-browser notes: create, edit, search and delete plain-text notes
Translation
Tiny EN/TH word-lookup demo with direction swap
Wiki
Read-only MDX wiki of technical pages with sections and tags