Ask HN: How will we integrate MCP servers in the future for all of our devtools?
Just curious what everybody thinks about how we will use MCP servers in the future. The thing I am stuck on is the future of the integration pattern.
Right now we go into our MCP client of choice like Claude, Cursor, and Windsurf and we manually add the servers ourselves after we done a bit of research to make sure it isn't too sketchy.
I think this is fine but what if we are working with multiple devtools at once, are we are going have 20-30 MCP servers integrated or added to Cursor. Not the end of the world and I guess it mimics sort of the like the VS Code Extension pattern, but I am wondering if a platform is just going to own all the integrations and we just connected one integration that manages the others?
Additionally is the new status quo going to be every devtool or developer service going to have a MCP service for their docs, SDKs, and REST APIs, and there will be a new vendor(although this probably exists already) as a service that just generates MCP servers for companies from their existing stack? And will it be as simple as them having a doc page that says copy this server link or run this npm command with prompts?
Anyways curious what folks think, I definitely have some ideas around MCP but I am still learning!
No comments yet.