Yeah, one way to think about it is like... protocols restrict things, so that people can expect the same stuff. With a traditional API, people can build it any

Yeah, one way to think about it is like... protocols restrict things, so that people can expect the same stuff. With a traditional API, people can build it any way they want, which means you (the client) need API docs. With MCP, you literally restrict it to 2 things: get the list of tools, and call the tool (using the schema you got above). Thus the key insight is just about: let's add 1 more endpoint that lists the APIs you have, so that robots can find it. Example time: - Build an MCP server (equivalent of "intro to flask 101"): https://developers.cloudflare.com/agents/guides/remote-mcp-server/ https://developers.cloudflare.com/agents/guides/remote-mcp-s... - Now you can add it to Claude Desktop/Cursor and see what it does - That's as far as i got lol