Skip to content

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

DevHub live preview
All projects

DevHub

Find a portfolio MCP endpoint and test a call in the browser.

The portfolio's MCP endpoints were spread across many apps with no single place to see their tools or try a call.

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

Each portfolio app exposed its own /api/mcp endpoint, with no single list of what tools each one offered.

After

Developer portal on the Reader shell: it lists the five endpoints and lets you send a test call to them.

How it's solved

Built a Next.js portal with a catalog of five MCP endpoints and their tools, a page per API, a quick-start doc, and a playground that sends JSON-RPC requests from the browser.

Trade-offs

Catalog metadata is hand-maintained and some tool names have drifted; cross-origin calls depend on each app's CORS.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev