Teddit

npx add-mcp 'https://teddit.io/mcp'

Teddit has an MCP server built in. Connect it to Claude, Cursor or another MCP client, and your own AI can read every answer, source and number in your workspace, manage prompts and competitors, and run scans if the key allows it.

What you get

The server is part of Teddit. There is nothing to install on our side or to deploy.

Item	Value
Address	https://teddit.io/mcp
Transport	Streamable HTTP, stateless: every request stands on its own, there is no session to keep open.
Authentication	Sign-in through OAuth 2.1 for Claude, Claude Code, Cursor and ChatGPT: the client sends you to Teddit, you pick the workspace, it works as you. For scripts, a workspace API key in the header Authorization: Bearer tdt_….
Contents	34 tools, one resource (teddit://projects) and two prompt templates (weekly_review, grow_prompt_set). All of them are listed in the tools reference.

Every tool call gets the same checks as the web app. A key can never do more than its access level allows, and nothing a tool does is hidden from the app: a scan started over MCP shows up in Scan history like any other.

Reading is free. One tool costs money: start_scan runs a scan, paid from the workspace balance. rewrite_queries is not charged, but it needs a balance above zero.

Keys for scripts and integrations

Most people never need a key: the clients above sign in through OAuth and work as the person who signed in. A key is for scripts, automations (n8n, Zapier, CI) and clients that can only send a header. It belongs to the workspace, has an access level of its own and keeps working when nobody is at the keyboard.

1. In the app, open your avatar in the top right, choose Workspace settings and then the API & MCP tab.
2. Press Create key. Give it a name that says where it will be used, for example “Claude on my laptop”.
3. Choose the access: Read only, Read and edit or Read, edit and run scans.
4. Copy the key. It starts with tdt_ and is shown once. Teddit keeps only a fingerprint of it and cannot show it again.

Anyone in the workspace can create a key; what it may do depends on their role. A key belongs to one workspace and is shown once; the dialog offers the Claude Code command with the key in it, ready to copy.

To take a key out of use, press the bin icon next to it. It stops working at once. More on keys: Authentication.

Claude

claude.ai, Claude Desktop and Claude Code

Add https://teddit.io/mcp as a custom connector (Settings → Connectors → Add custom connector). Claude sends you to Teddit to sign in, you pick the workspace and the access (Read and edit by default: it sets things up but never runs scans or spends), and the connector works as you within that access and on your sites. No key is needed, and you can disconnect it under Account → Connected apps. The same works in Claude Code: claude mcp add --transport http teddit https://teddit.io/mcp, then /mcp to sign in.

Claude Code with a key

For a shared or scripted set-up, the key does instead of the sign-in:

claude mcp add --transport http teddit https://teddit.io/mcp \
  --header "Authorization: Bearer tdt_…"

Claude Desktop

Claude Desktop starts MCP servers as local programs from its config file. A small bridge, the open-source mcp-remote package, connects it to Teddit’s address and sends the key. It needs Node.js. Add this to claude_desktop_config.json and restart Claude:

{
  "mcpServers": {
    "teddit": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://teddit.io/mcp", "--header", "Authorization:${TEDDIT_AUTH}"],
      "env": {
        "TEDDIT_AUTH": "Bearer tdt_…"
      }
    }
  }
}

The key goes in TEDDIT_AUTH, after Bearer and a space.

ChatGPT

ChatGPT adds remote MCP servers as connectors, by address, in developer mode (Settings → Connectors → Create). Paste the address and choose OAuth: ChatGPT sends you to Teddit to sign in and pick the workspace.

Name:  Teddit
URL:   https://teddit.io/mcp
Auth:  OAuth

Teddit signs clients in through OAuth 2.1 (with PKCE, dynamic client registration and Client ID Metadata Documents), so a connector form that offers only OAuth works: enter the address, sign in with your Teddit account, pick the workspace. A key in the Authorization header works as before.

Cursor and other clients

Any client that speaks MCP over Streamable HTTP works. For Cursor, put this in .cursor/mcp.json; on first use the client opens the Teddit sign-in:

{
  "mcpServers": {
    "teddit": {
      "type": "http",
      "url": "https://teddit.io/mcp"
    }
  }
}

For a client you configure by hand, these are the facts it needs:

• the address https://teddit.io/mcp;
• the transport: Streamable HTTP;
• sign-in through OAuth 2.1 (dynamic client registration or a Client ID Metadata Document, PKCE S256), or, for a client that can only send a header, a key as Authorization: Bearer tdt_….

A client that can only start local programs can use the mcp-remote bridge shown under Claude Desktop.

Check the connection

Ask your AI: “Use Teddit and tell me which workspace you are connected to.” It should call whoami and answer with the workspace name and the role it works with: yours when it signed in, the key’s when it uses one.

To test a key without any client, call the API directly:

curl https://teddit.io/api/whoami \
  -H "Authorization: Bearer tdt_…"

What you see	What it means
HTTP 401 from /mcp	Nothing signed the request: no OAuth token and no key, the header is not in the form Bearer …, or the key or connection was revoked. The 401 carries the address of the sign-in metadata, which is how an OAuth client knows to start the sign-in.
A tool answers Error: You do not have permission to do that.	The key’s access level is too low for that tool. Create a key with more access.
A tool answers Error: Project not found.	The site id is wrong, or the site belongs to another workspace. Ids come from list_projects.

What a key may do

Access	Tools it can use
Read only	Everything that reads: reports, trends, prompts and their answers, competitors, pages, scan history and progress, cost estimates, charts.
Read and edit	The above, and: add, edit, pause, import and delete prompts; add, edit and remove buyer personas and competitors; change a site’s settings; read the sitemap again.
Read, edit and run scans	The above, and: start and cancel scans, rewrite imported queries as questions, and add a site.

You cannot create a key with more access than you have yourself. Scans started with a key are paid from the same balance and count against the same limits as scans started in the app, and are recorded under the name of the person who created the key.

Next: the tools reference and some example questions.