Token-Based Setup

Overview

Cursor, Windsurf, VS Code, and other MCP-compatible editors don’t support OAuth natively. Instead, you authenticate with a personal access token passed as a Bearer header. The setup takes about a minute.

Generating a Token

  1. Log in to your TransformSEO dashboard.
  2. Go to the Getting Started page (under Setup in the sidebar).
  3. Your API token is displayed in the setup panel. Click Copy to copy it to your clipboard.

Each token is scoped to your account and team. Keep it private — anyone with your token can make API calls on your behalf.

Cursor

Create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "transformseo": {
      "url": "https://gettransformseo.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace YOUR_TOKEN_HERE with the token you copied. Restart Cursor to activate.

Windsurf

Create or edit .windsurf/mcp.json in your project root:

{
  "mcpServers": {
    "transformseo": {
      "url": "https://gettransformseo.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

VS Code

Create or edit .vscode/mcp.json in your project root. Note that VS Code uses a servers key instead of mcpServers:

{
  "servers": {
    "transformseo": {
      "type": "sse",
      "url": "https://gettransformseo.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Other MCP-Compatible Editors

Most MCP clients follow the same pattern. Add a server entry with these values:

  • URL: https://gettransformseo.com/mcp
  • Header: Authorization: Bearer YOUR_TOKEN_HERE
  • Transport: SSE (Server-Sent Events) or Streamable HTTP, depending on what the client supports

Consult your editor’s MCP documentation for the exact config file location and format.

Token Management

  • Regenerating a token — On the Getting Started page, click Regenerate to create a new token. Your old token is immediately invalidated, so update any editor configs that use it.
  • Last used — The Getting Started page shows when your token was last used, so you can verify your connection is working.
  • One token per team — Your token is tied to the currently selected team. If you switch teams, you’ll need to use the token for that team.

Troubleshooting

  • 401 Unauthorized — Double-check that the token is correct and hasn’t been regenerated since you copied it.
  • Tools not loading — Make sure the config file is in the right location for your editor and the JSON is valid.
  • Editor doesn’t detect the server — Restart the editor after adding the config. Some editors require a manual reload.