Connect Cursor, VS Code and Other MCP Clients

Any MCP client that connects to remote servers over Streamable HTTP and can either sign in with OAuth or send an Authorization header can connect to Traffic Creator:

  • Address: https://traffic-creator.com/mcp
  • Sign-in: OAuth with your Traffic Creator account, or
  • API key: the header Authorization: Bearer <key> with a key from API & MCP (see Create, use and revoke API keys).

The Cursor and Gemini CLI examples read the key from the environment variable TRAFFIC_CREATOR_API_KEY, and VS Code asks for it once and stores it securely, so the key never ends up in a file you might share.

Cursor#

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "traffic-creator": {
      "url": "https://traffic-creator.com/mcp",
      "headers": { "Authorization": "Bearer ${env:TRAFFIC_CREATOR_API_KEY}" }
    }
  }
}

Save the file and restart Cursor. The server then appears under Customize → MCPs, where you can turn it off or remove it. If Cursor ignores the key and asks you to sign in, sign in instead: Cursor currently prefers sign-in for servers that offer it.

To sign in instead of using a key, leave out headers, then follow Cursor's sign-in prompt for the server under Customize → MCPs.

By default, Cursor runs tools on your allowlist straight away and lets its safety check decide about the rest, asking you when needed. To be asked every time, choose a different run mode under Cursor Settings → Agents → Approvals & Execution.

VS Code (GitHub Copilot)#

Add this to .vscode/mcp.json in your project. VS Code asks for the key the first time and stores it securely:

{
  "inputs": [
    { "type": "promptString", "id": "tc-api-key", "description": "Traffic Creator API key", "password": true }
  ],
  "servers": {
    "traffic-creator": {
      "type": "http",
      "url": "https://traffic-creator.com/mcp",
      "headers": { "Authorization": "Bearer ${input:tc-api-key}" }
    }
  }
}

To sign in instead, leave out inputs and headers: a browser window opens for the Traffic Creator sign-in on the first connection. In the Agents window, sign in instead of using a key: VS Code does not pass servers that ask for a key to agent sessions.

On Copilot Business and Enterprise, an admin must first turn on the MCP servers in Copilot policy, which is off by default. If your company only allows listed MCP servers, https://traffic-creator.com/mcp must be on that list.

Gemini CLI#

gemini mcp add -s user --transport http traffic-creator https://traffic-creator.com/mcp

Then sign in with /mcp auth traffic-creator inside Gemini CLI. -s user adds the server for all projects.

To use a key instead, run:

gemini mcp add -s user --transport http -H 'Authorization: Bearer ${TRAFFIC_CREATOR_API_KEY}' traffic-creator https://traffic-creator.com/mcp

The single quotes keep the key out of the settings file. Check with gemini mcp list that the server is connected.

Automation Tools (n8n, Zapier, Make)#

n8n, Zapier and Make have MCP client steps, but Zapier's and Make's are still in beta. For automations you rely on, use the Account API with an X-API-KEY header instead: it is the same functionality with fixed, documented routes.

Remove a Client#

Remove the server entry from the client's settings, then revoke its key under API & MCP → Your keys, or disconnect it under Connected apps if you signed in.

Loading Traffic Creator