Model Context Protocol (MCP) servers are a convenient way to allow AI applications (Claude, Gemini, ChatGPT, etc.) to connect to your product. We have a deep dive on MCP that will cover what it is and how it works. In this blog post, we’re going to set up our

Model Context Protocol (MCP) servers are a convenient way to allow AI applications (Claude, Gemini, ChatGPT, etc.) to connect to your product. In this blog post, we’re going to set up our own MCP server, add authentication to it, and deploy it as a Cloudflare Worker. If you are

Model Context Protocol (MCP) is a standard for connecting AI applications (ChatGPT, Claude, Gemini, OpenCode) to external systems (Google, GitHub, Your Product). In this post, we’re going to look at what it is, why your users may care, and what it actually means to “support MCP.” An example product

MCP servers are just a clean way to give an AI client (like Claude Desktop, Claude Code, ChatGPT, etc) a set of functions it can call. This can really be anything, like: * A function that fetches the weather for a date/zip code * A function that loads your calendar data

Model Context Protocol (MCP) is a standard for connecting AI applications (Claude, ChatGPT, Gemini) to external applications (Linear, Google Calendar, some custom code you write). It’s a popular way to give those AI applications more context. You can ask ChatGPT a question like Can you get me a list

Dynamic Client Registration (DCR) is an extension of OAuth that allows OAuth clients to be created programmatically. It wasn’t a very popular extension until recently, when the Model Context Protocol (MCP) spec brought it back into the conversation as a recommended option (though newer versions of the spec are