This is really interesting. Has anyone seen a good registry of MCP servers somewhere? What I would love to be able to do is ask for a task and have the agent figure out what servers and tools it needs to accomplish that task directly.
There's a number of people building various flavors of this. I'm one of them -- pulsemcp.com - we expose our data via API (pulsemcp.com/api) that is theoretically the starting point for what you're asking.
The issue with the current state of the ecosystem to do what you're saying is that server implementations all have extreme variances of quality. Some are very robust and reliable. Others have very poor and limited UX, if you can even get them to start up on your local machine.
So we're not really in a place where we can trust that a server "does what it says it can do [well]", and so any autonomous solution to "choose tools (servers)" probably won't work well today (yet) while the signal to noise ratio is poor.
Personally: I think autonomously choosing between tools is not the most compelling approach in the short to medium time horizon. I expect client application creators to get a lot of mileage by thoughtfully curating the possible servers exposed to their users, and building nice UX to integrate usage of relevant servers as-needed.
I've seen a number of them. Some are a simple listing, others do some level of validation and ranking based on various heuristics, others are an actual service that will run the mcp servers for you in an encapsulated form so that it becomes more of an app store-like experience and you don't need to do manual configuration in your client. mcp.run is basically this - they run the servers in a webassembly sandbox for you. I'm probably not doing it real justice, but it's a really interesting concept in a very interesting space(MCP) right now.
This is something I have thought a little bit about. I think a registry would be useful and I know a few projects trying to set that up, but there may be multiple MCP servers for the same thing (already there are a few community implementations of an Atlassian server for e.g.).
It is conceivable that we make it completely dynamic where the agent first decides which set of servers it should need for its task/instruction. Another way of framing that is it should be possible to create agents themselves dynamically based on the objective.
I don’t have a good answer to this yet but if you want to help figure that out we can collaborate
auntad|1 year ago
The issue with the current state of the ecosystem to do what you're saying is that server implementations all have extreme variances of quality. Some are very robust and reliable. Others have very poor and limited UX, if you can even get them to start up on your local machine.
So we're not really in a place where we can trust that a server "does what it says it can do [well]", and so any autonomous solution to "choose tools (servers)" probably won't work well today (yet) while the signal to noise ratio is poor.
Personally: I think autonomously choosing between tools is not the most compelling approach in the short to medium time horizon. I expect client application creators to get a lot of mileage by thoughtfully curating the possible servers exposed to their users, and building nice UX to integrate usage of relevant servers as-needed.
knowaveragejoe|1 year ago
https://glama.ai/mcp/servers/
https://www.mcp.run/
saqadri|1 year ago
It is conceivable that we make it completely dynamic where the agent first decides which set of servers it should need for its task/instruction. Another way of framing that is it should be possible to create agents themselves dynamically based on the objective.
I don’t have a good answer to this yet but if you want to help figure that out we can collaborate
dSebastien|1 year ago
saqadri|1 year ago
nilslice|1 year ago
travisennis|1 year ago
[deleted]