Skip to main content

Topic Hub

MCP

The Model Context Protocol turns a website from something agents scrape into something they can call. These articles cover building an MCP server, deploying it on Cloudflare Workers, OAuth scopes, and write-tool permissions — from a server that actually ships on this site.

MCPJSON-RPCCloudflare WorkersOAuth

Articles 9

Frequently Asked Questions

What is the Model Context Protocol (MCP)?

MCP is an open protocol that lets AI agents call typed tools over JSON-RPC instead of scraping web pages. A server exposes tools/list and tools/call; a client (Claude, Cursor, ChatGPT) discovers those tools and invokes them. The usual transport is Streamable HTTP — one POST /mcp endpoint.

How do I build an MCP server?

You need four JSON-RPC methods: initialize, tools/list, tools/call, and ping. A stateless Cloudflare Worker that returns plain JSON is fully spec-compliant. Back the tools with data you already publish (a JSON feed, Markdown pages) so there is one source of truth. Full walkthrough: https://umesh-malik.com/blog/how-to-build-mcp-server.

Do MCP servers need authentication?

Public read-only tools can stay anonymous. Write tools and private data need OAuth (or a similar token). Optional OAuth scopes let the user narrow permissions at consent time so an agent does not get a broader grant than the task needs.

Where should I host an MCP server?

Anywhere that can serve HTTPS JSON. Cloudflare Workers is a common fit: one file, a free tier, and you can pin the Worker to /mcp so the rest of a static site stays on the asset worker. Guide: https://umesh-malik.com/blog/deploy-mcp-server-cloudflare-workers.

Google Search · Preferred sources

Prefer this site on Google

If you already read this writing, add umesh-malik.com as a Preferred Source. Google can then highlight it with a preferred badge in Top Stories, AI Overviews, and AI Mode — for you, not as a site-wide ranking boost.