Cursor MCP server for a phone line
A Cursor MCP server for a phone line is a remote URL in a JSON file, plus a key that can look and not change anything. You are not installing a phone app inside the editor. Cursor's MCP documentation, opened 15 November 2026, says a remote server is a url and optional headers. RingKit's server is https://api.ringkit.com/mcp. The file looks like this:
{
"mcpServers": {
"ringkit": {
"url": "https://api.ringkit.com/mcp",
"headers": {
"Authorization": "Bearer ${env:RINGKIT_READ_KEY}"
}
}
}
}
That is the whole connection. The same page says Cursor resolves ${env:NAME} inside headers. The key stays in the environment. The JSON can sit in a repo without the secret. For a custom server, that page says you update the local files and restart Cursor. Leave command out. The docs use command for a program Cursor starts on your machine. This server is already running at the URL. A local program entry will not reach the phone API.
Where Cursor reads the file
The docs give two paths. .cursor/mcp.json in the project is the project file. ~/.cursor/mcp.json in your home directory is the one available in every project. Use the project file when this repo is the only place that should see the phone tools. Use the home file when you want the same server while you move between repos. Do not put a raw rk_… string in the project file. Anyone who clones the repo would hold a key that acts on a business.
The page also says Cursor asks before it runs an MCP tool, unless you have changed that. Leave the prompt on. A tool that orders a number or rewrites the brief should not run because a sentence in chat sounded like a request. If the connection fails, the same page says the Output panel has an "MCP Logs" entry. That log is where a refused header shows up. It is not a second configuration file.
Put a read key in the header
A key returned when a business is created is scope manage. It acts as the owner. It can order a number, change the brief, and invite the owner. That is the wrong key for an editor you use to ask what yesterday's callers wanted.
Create a second key with the manage key, once:
curl https://api.ringkit.com/v1/businesses/$BIZ/api-keys \
-H "Authorization: Bearer $RINGKIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "name": "Cursor reporting", "scope": "read" }'
The plaintext comes back once. Put it in RINGKIT_READ_KEY, in the environment Cursor starts from. The docs say remote servers do not read an envFile. Scope read can GET. Anything else returns 403 insufficient_scope. The docs say the same thing for REST: give a reporting tool a read key. Cursor's security notes on that MCP page say to limit a key to the permissions you need. A read key is that limit. Listing calls and reading one call are GET. Creating a webhook, ordering a number, and replacing the brief are not.
The manage key stays out of mcp.json. Revoke the read key with DELETE /v1/businesses/$BIZ/api-keys/:keyId when the person who had it leaves. The key list does not show the secret again. If you lose it, make another and revoke the old one.
When the business does not exist yet
A read key needs a business. ringkit_create_business is the tool that works with no Authorization header. Connect without the header, create the business, and store the key the tool returns. That key is shown once, and it is a manage key. Reconnect with it only long enough to write the brief and, after a person has paid, to order the number. Then mint the read key and point Cursor at that. The tool order, and the two steps a person still has to do, is MCP phone receptionist. What the number is, once it exists, is AI agent phone number.
Do not point this file at https://api.ringkit.com/mcp/oauth and expect the JSON above to sign a person in. That path is the OAuth connector. This page is the API-key file the product docs show for Cursor. There is no client library to install. The receptionist answers from the brief, transfers to numbers you listed, and takes a message otherwise. It does not book a calendar from the editor.