Cursor setup

Connect ziptie.ai to Cursor so the AI can query your tracked prompts, metrics, and competitor data while you work.

Prerequisites

• Cursor installed (any version supporting MCP).
• A ziptie.ai API token with at least read scope. Create one under Project Settings > API & MCP access, or a workspace token from Workspace Settings > API & MCP access for one token that reaches every project. The workspace needs the paid API & MCP access add-on active first - without it the create button is disabled and existing tokens are rejected with API_ADDON_INACTIVE. See authentication.

Configuration

Open Cursor settings, go to Features > MCP, and add a new server. Paste the following configuration:

{
  "mcpServers": {
    "ziptie": {
      "url": "https://api.ziptie.ai/mcp",
      "headers": {
        "Authorization": "Bearer zt_live_<your-token>"
      }
    }
  }
}

Replace zt_live_<your-token> with your actual token. The top-level mcpServers wrapper is required; only the per-server "type": "http" field is omitted, because Cursor infers the transport from the url string.

Alternatively, edit ~/.cursor/mcp.json (global) or <project>/.cursor/mcp.json (project-scoped) directly using the same JSON above.

Restart Cursor

After saving, restart Cursor or reload the MCP server list from settings. The ziptie.ai tools appear in the Cursor AI panel.

Verify the connection

In the Cursor AI chat, ask:

"List my ziptie.ai prompts for project PROJECT_ID"

Cursor will call the list_prompts tool and display the results.

Troubleshooting

-32001 Unauthorized The token is expired, revoked, or incorrectly copied. Create a new token and update the Authorization header value in the config. Read error.data.code for which of those it is; the HTTP status is 200 either way.

Empty tool list or "server not responding" Verify the URL is https://api.ziptie.ai/mcp with no trailing slash. Check that the Authorization header value starts with the Bearer keyword followed by a single space, then the token.

-32004 with data.code API_ADDON_INACTIVE or PAYMENT_REQUIRED The token is valid; the workspace is not entitled. API_ADDON_INACTIVE means the API & MCP access add-on is off - it lapsed, or the subscription was cancelled - and PAYMENT_REQUIRED means the subscription payment is overdue. Entitlement is checked before any tool runs, so the handshake itself fails and no tools load. Fix it in workspace billing settings; the token does not need replacing. See MCP overview.

Tools appear but calls fail The token may not have sufficient scope for the operation. Write and delete operations require write or admin scope respectively. Create a token with the appropriate scope.