jspahrsummers

3 ms·

1.
by jspahrsummers 2y ago
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 https:&#x2
2.
by jspahrsummers 2y ago
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!
3.
by jspahrsummers 2y ago
Definitely not geolocked! Please try the debugging guide here: https://modelcontextprotocol.io/docs/tools/debugging
4.
by jspahrsummers 2y ago
There's a debugging guide here that may be helpful: https://modelcontextprotocol.io/docs/tools/debugging
5.
by jspahrsummers 2y ago
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 at a ti
6.
by jspahrsummers 2y ago
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 concepts of "prompts
7.
by jspahrsummers 2y ago
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 https://spec.modelcontex
8.
by jspahrsummers 2y ago
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 community c
9.
by jspahrsummers 2y ago
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 injection and mi
10.
by jspahrsummers 2y ago
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...
11.
by jspahrsummers 2y ago
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 ver
12.
by jspahrsummers 2y ago
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/
13.
by jspahrsummers 2y ago
Already available in the latest at https://claude.ai/download !
14.
by jspahrsummers 2y ago
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 be that to the applica
15.
by jspahrsummers 13y ago
We do need some examples, but the headers are documented quite extensively, FWIW.