Turbo Notify in Cursor

In Cursor, Turbo Notify comes in as an MCP server, set up in the mcp.json file, and the virtual attendant skill is installed separately, with npx skills. Here the attendant works in assisted mode: a person approves every answer, and nothing is answered while Cursor is closed.

What you need

• A Turbo Notify account with a connected number (quickstart).
• Cursor installed.
• For the skill: Node.js 22.20 or newer (required by npx skills) and Python 3.9 or newer.

Connect

Create the file .cursor/mcp.json in the project, or ~/.cursor/mcp.json to apply to every project:

mcp.json

{
  "mcpServers": {
    "turbo-notify": {
      "url": "https://mcp.turbonotify.com"
    }
  }
}

The skill:

npx skills add turbo-notify/agent-skills -a cursor

Without -g, the skill stays in the current project’s folder. With -g, it applies to every project.

Sign in

• With your account: Cursor signs in to remote servers through the server’s own sign-in. When you connect turbo-notify in the MCP server list (under Customize), it asks for the Turbo Notify sign-in in your browser. Sign in and approve access.

• With an API key: create the key in API Keys (opens in a new tab) and add the header to the file:

  mcp.json

  {
    "mcpServers": {
      "turbo-notify": {
        "url": "https://mcp.turbonotify.com",
        "headers": {
          "Authorization": "Bearer YOUR_KEY"
        }
      }
    }
  }

  Treat the key like a password and do not commit this file to a repository.

Scopes and keys are in MCP server.

Test

Open Cursor’s chat and ask: “List my WhatsApp numbers on Turbo Notify.” The agent calls list_numbers, which only reads. If it asks permission for the tool, approve.

Update

npx skills update

The MCP server needs no update: the address is always the same.

Limits

• Assisted mode only, with you present. Every answer needs approval.
• The tools follow the API limits: 600 requests per minute per key or sign-in, plus the plan’s quota and sending pace. See MCP server limits.

What is not verified

• The Cursor app itself. Registration, approval, the return to cursor://anysphere.cursor-mcp/oauth/callback, the code exchange and a list_numbers call were checked on 3 November 2026 against the server with the same request Cursor sends; the application was not run.
• The skill inside Cursor. The install follows the npx skills documentation, and we have not run the attendant in this agent.