In Cursor’s GitHub issues page for adding MCP servers, GitHub · Where software is built , there is a backlog of open requests stretching back to September, 2025.
Does Cursor have someone assigned to look at these requests and process them in a timely manner? Will an issue (MCP server addition request) be closed with a status indicating whether the MCP server was approved or not?
If an MCP server request isn’t approved, will Cursor add comments indicating the reason for rejection?
(Edit: paging @deanrie to see if I can get an answer to this one.)
With the introduction of Plugins and the Marketplace, we’re reevaluating how MCP server integrations are handled. Plugins are a more flexible and scalable path forward since they can bundle MCP servers alongside rules, skills, agents, and more into a single distributable package.
If you’re looking to get an MCP server into Cursor, we’d encourage building it as a plugin and submitting it to the marketplace. That’s the best way to get it in front of users going forward!
Thanks, @Colin! Sam ([email protected]) led me astray in this respect by recommending that an issue be opened in GitHub for this purpose, so you might want to update your AI and add a note in GitHub to this effect; I see a lot of other people and companies following the same route I took.
