https://github.com/jspahrsummers
You can find more information on some design questions like these in https://spec.modelcontextprotocol.io/specification, which is a much more "implementors" focused guide than the user documentation at…
We're still in the process of thinking through and fleshing out full details for remote MCP connections. This is definitely a good idea to include in the mix!
Definitely not geolocked! Please try the debugging guide here: https://modelcontextprotocol.io/docs/tools/debugging
There's a debugging guide here that may be helpful: https://modelcontextprotocol.io/docs/tools/debugging
Your concerns are very valid. This is partly why right now, in Claude Desktop, it's not possible to grant permission permanently. The most you can do is "Allow for this chat," which applies to one tool from one server…
We definitely hope this will solve the NxM problem. On tools specifically, we went back and forth about whether the other primitives of MCP ultimately just reduce to tool use, but ultimately concluded that separate…
Our thinking is that prompts will generally be a user initiated feature of some kind. These docs go into a bit more detail: https://modelcontextprotocol.io/docs/concepts/prompts…
This is a great idea! There's also the matter of requests' result types not being automatically inferred in the SDK right now, which would be great to fix. Could I convince you to submit a PR? We'd love to include…
We do want to improve this over time, just trying to find the right balance between usability and security. Although MCP is powerful and we hope it'll really unlock a lot of potential, there are still risks like prompt…
We're definitely interested in extending MCP to cover remote connections as well. Both SDKs already support an SSE transport with that in mind: https://modelcontextprotocol.io/docs/concepts/transports#ser... However,…
You can read how we're implementing versioning here: https://spec.modelcontextprotocol.io/specification/basic/ver... It's not exactly immutable, but any backwards incompatible changes would require a version bump. We…
Sorry, I think that's just the nav on those docs being confusing (particularly on mobile). You can see the spec here: https://spec.modelcontextprotocol.io/specification/
Already available in the latest at https://claude.ai/download!
Probably, yes! You could imagine building an MCP server (integration) for a particular piece of legacy software, and inside that server, you could employ Computer Use to actually use and automate it. The benefit would…
We do need some examples, but the headers are documented quite extensively, FWIW.
You can find more information on some design questions like these in https://spec.modelcontextprotocol.io/specification, which is a much more "implementors" focused guide than the user documentation at…
We're still in the process of thinking through and fleshing out full details for remote MCP connections. This is definitely a good idea to include in the mix!
Definitely not geolocked! Please try the debugging guide here: https://modelcontextprotocol.io/docs/tools/debugging
There's a debugging guide here that may be helpful: https://modelcontextprotocol.io/docs/tools/debugging
Your concerns are very valid. This is partly why right now, in Claude Desktop, it's not possible to grant permission permanently. The most you can do is "Allow for this chat," which applies to one tool from one server…
We definitely hope this will solve the NxM problem. On tools specifically, we went back and forth about whether the other primitives of MCP ultimately just reduce to tool use, but ultimately concluded that separate…
Our thinking is that prompts will generally be a user initiated feature of some kind. These docs go into a bit more detail: https://modelcontextprotocol.io/docs/concepts/prompts…
This is a great idea! There's also the matter of requests' result types not being automatically inferred in the SDK right now, which would be great to fix. Could I convince you to submit a PR? We'd love to include…
We do want to improve this over time, just trying to find the right balance between usability and security. Although MCP is powerful and we hope it'll really unlock a lot of potential, there are still risks like prompt…
We're definitely interested in extending MCP to cover remote connections as well. Both SDKs already support an SSE transport with that in mind: https://modelcontextprotocol.io/docs/concepts/transports#ser... However,…
You can read how we're implementing versioning here: https://spec.modelcontextprotocol.io/specification/basic/ver... It's not exactly immutable, but any backwards incompatible changes would require a version bump. We…
Sorry, I think that's just the nav on those docs being confusing (particularly on mobile). You can see the spec here: https://spec.modelcontextprotocol.io/specification/
Already available in the latest at https://claude.ai/download!
Probably, yes! You could imagine building an MCP server (integration) for a particular piece of legacy software, and inside that server, you could employ Computer Use to actually use and automate it. The benefit would…
We do need some examples, but the headers are documented quite extensively, FWIW.