Skip to main content

​
Prerequisites

Before you begin, make sure you have:
  1. A paid Superlines plan (Starter, Growth, or Enterprise)
  2. An API key from Organization Settings (format: sl_live_...) — not required for OAuth on Claude.ai
  3. An MCP-compatible client installed

​
Connection methods

MethodBest forProtocol
OAuth (Claude.ai)Claude.ai web — no API key neededOAuth 2.0 + SSE
SSE (URL-based)Claude Desktop, most clientsServer-Sent Events
Local npxCursor, VS Code, advanced setupsStandard I/O

​
Option 1: OAuth setup (Claude.ai)

Connect Superlines directly to Claude.ai through OAuth — no API key required. You sign in with your Superlines account and authorize access.
1

Open Claude.ai settings

Go to claude.ai → Settings → Connectors → Add custom connector.
2

Enter the server details

  • Name: Superlines
  • URL: https://mcpsse.superlines.io
  • Open Advanced settings and set OAuth Client ID to anthropic-claude
  • Leave OAuth Client Secret blank
  • Click Add
3

Authorize access

Claude will redirect you to the Superlines authorization page. Sign in with your Superlines account, review the requested permissions, select which brands to share, and click Authorize Access.
4

Start using Superlines

Back in Claude, start a new conversation and try: “List my Superlines brands”
OAuth connections are scoped to the brands you select during authorization. You can revoke access at any time from your Superlines account settings.

​
Option 2: SSE / URL-based setup

The simplest approach — just add a URL to your client’s configuration. Connection URL: 
https://mcpsse.superlines.io?token=YOUR_API_KEY
Replace YOUR_API_KEY with your actual API key.
1

Open Claude Desktop settings

Go to Settings → Developer → Edit Config to open:
~/Library/Application Support/Claude/claude_desktop_config.json
2

Add the Superlines server

{
  "mcpServers": {
    "superlines": {
      "url": "https://mcpsse.superlines.io?token=YOUR_API_KEY",
      "transport": "sse"
    }
  }
}
3

Restart Claude Desktop

Save and fully restart the app for changes to take effect.

​
Option 3: Local npx setup

For clients that prefer local process-based connections, use the npm package.
Requires Node.js installed on your machine.
{
  "mcpServers": {
    "superlines": {
      "command": "npx",
      "args": ["-y", "@superlines/mcp-server"],
      "env": {
        "SUPERLINES_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

​
API key permissions

By default, API keys have read-only access — they can query analytics data but cannot modify your account. To use the Account Management tools (creating brands, adding prompts, etc.), you need to enable write permissions on your API key.

​
How to enable write permissions

1

Go to Organization Settings

Open Organization Settings → API Keys in the Superlines dashboard.
2

Edit your API key

Click on the API key you use for MCP and open its permissions settings.
3

Enable write permissions

Toggle on the permissions you need:
  • write:brands — allows creating new brands/domains
  • write:prompts — allows adding, pausing, unpausing prompts and managing labels
4

Save and reconnect

Save your changes. No client restart is needed — permissions take effect immediately.

​
Available permissions

PermissionGrants access to
readAll analytics and reporting tools (default, always included)
write:brandscreate_brand, get_brand_setup_status
write:promptsadd_prompts, pause_prompts, unpause_prompts, update_prompt_labels
Write operations are rate-limited and audit-logged for security. Brand creation is limited to 5 per hour, and prompt operations to 100 per hour per organization. All write actions are recorded in your organization’s audit log.
Deletion is intentionally not supported via MCP to prevent accidental data loss. Use pause_prompts to temporarily disable prompts instead.

​
Verify the connection

After setting up your client:
  1. Start a new conversation
  2. Ask: “List my Superlines brands”
  3. The AI should call the list_brands tool and show your brands
If it works, try:
  • “Show me my brand visibility for the last 30 days”
  • “Who are my top competitors?”
  • “Find content opportunities where I have low visibility”

​
Troubleshooting

IssueSolution
”Tool not found”Restart your MCP client after configuration changes
”Authentication failed”Verify your API key is correct and starts with sl_live_
”No data returned”Make sure you have at least one brand with tracked prompts
”Connection timeout”Check your internet connection; the SSE endpoint is at mcpsse.superlines.io
”Plan not supported”MCP requires a paid plan (Starter, Growth, or Enterprise)
Never share your API key publicly. If compromised, revoke it immediately in Organization Settings and generate a new one.

​
Resources