Cursor keeps MCP servers in a JSON file and gives you a settings screen for editing it. Either route takes the same address, and the dashboard also builds a link that does it in one press.
By the settings screen
Open Cursor's settings and find MCP — it has sat under Tools, under Integrations and under Features, depending on the version. Add a server, give it a name, and paste the address as its url. Leave the headers and the authentication empty.
By the file
The same thing written by hand. In ~/.cursor/mcp.json it is on everywhere; in a project's own .cursor/mcp.json it has to be switched on once in that settings screen before the agent will use it.
{
"mcpServers": {
"makehybrid": { "url": "https://makehybrid.com/mcp/<your key>" }
}
}
One field. A url and a command in the same entry is a server described two ways, and clients reject it.
By the install link
The dashboard shows an Add it to Cursor button beside the address. It is a cursor:// link with that entry inside it, which Cursor opens as “install this server?”. The link carries your key, so it is built in your own browser and is as private as the address itself.
Questions people ask
Why would an editor want my LinkedIn?
Because the API is not only LinkedIn. The same connection carries the messaging channels and the project rooms, so the agent that writes your code can also answer the customer who wrote in about it.
Does this work in VS Code, Zed or anything else?
Any client that speaks MCP over HTTP takes the same single address. If it asks for a transport, it is a remote server over HTTP, not a command to run.
Where does the key end up?
In the file you put it in, on your own machine. Nothing about the connector is stored on our side beyond the key itself, which you can revoke whenever you like.