Cursor

Cursor

A short entry in mcp.json.

Server URL
https://mcp.glitchads.ai/mcp

Adding the server

Add the server per project in .cursor/mcp.json or globally in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "glitch": {
      "url": "https://mcp.glitchads.ai/mcp"
    }
  }
}

For something headless, pass an API key instead. Cursor reads environment variables in that field, as the sample shows, so the file never holds the key itself:

{
  "mcpServers": {
    "glitch": {
      "url": "https://mcp.glitchads.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:GLITCH_API_KEY}"
      }
    }
  }
}

Without a header, Cursor uses OAuth: follow its authentication prompts to sign in to Glitch and approve the scopes. Servers are switched on and off under Customize, then MCPs.

Approvals

Cursor's Run Mode, under Settings, then Agents, then Approvals & Execution, decides when the agent asks before a tool call. In Auto-review, the default from Cursor 3.6, allowlisted tools run immediately and a classifier reviews the rest, so a write tool can run without asking you. To be asked before every change to your Google Ads account, choose Allowlist and keep the glitch_* write tools off the allowlist.

Check it worked

  • Customize, then MCPs, lists glitch.
  • The tool list shows 21 tools named glitch_*.

Ask: "List my Glitch organizations." You should get back the organizations your connection covers, with your role in each.

Troubleshooting

The server does not connect If you did not set a header, finish the authentication prompts. Check the server is switched on under Customize, then MCPs.
insufficient_scope The error names the scope that is missing. Authenticate the server again, approving the extra access. If your Glitch role does not allow it, ask an organization Admin or Owner.
org_access_denied The organization slug is wrong, your Glitch user is not a member of that organization, or the membership ended. glitch_list_organizations shows the slugs you can use.
Revoking access Remove the server from mcp.json, or revoke it in Glitch under Account, API Keys, Connected apps. Either stops access on the next request.

Next