
Linkeddit is agent-first: connect 34 tools for competitor moves, measured AI recommendations, Google rankings and Search Console. Linkeddit supplies the evidence and persistent results; Claude helps you reason and draft in your own context. Authorize with your account, without generating an API key.
In Claude.ai, go to Settings > Connectors > Add custom connector and paste the connector URL https://mcp.linkeddit.com/mcp. When Claude asks for an OAuth Client ID, enter linkeddit-mcp-claude and leave the Client Secret blank. Authorize once with your Linkeddit account and all 34 tools are available, with no API keys.
Connecting Cursor, VS Code, or Claude Desktop too? See the MCP server overview for every supported client, or the connector docs.
Connector URL
https://mcp.linkeddit.com/mcp
OAuth Client ID
linkeddit-mcp-claude
Client secret
Not required, public PKCE client
Claude will say automatic client registration is not supported. That is expected. Linkeddit uses pre-registered public clients, so you paste the Client ID once and never handle a secret.
Every tool is callable directly from any Claude conversation.
Measure where ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews, and Google AI Mode recommend someone else on your buying questions, then work each gap from recorded evidence.
Graded competitor briefs, complaint themes, pricing and landing-page changes, and the switching signals behind them.
Where your tracked keywords rank on Google, scored keywords, live SERP and autocomplete data, and the queries real buyers used to reach your site.
Claude.ai
Native OAuth
Claude Desktop
mcp-remote
Claude Code
HTTP
Cursor
mcp-remote
VS Code
HTTP
Windsurf
mcp-remote
Where are AI answer engines recommending competitors instead of us?
Using answer_gaps_get
14 recommendation gaps this run. The largest: on “best CRM for small agencies” three of six engines recommend two competitors and cite the same comparison page, which does not mention you...
Pull the complaints about that competitor, then draft the brief that closes the gap
Using compete_brief_get, then answer_fix_draft
Customers of that competitor cluster on pricing surprises and a slow import. Here is the brief, built from the citations the engines actually used plus those complaints...
Full authorization code flow with proof key for code exchange. Nothing to paste, nothing to store on your side.
Short-lived, signed access tokens bound to the connector endpoint. A token minted for anything else is rejected.
Every tool reads only your own projects, briefs, and audit runs. There is no cross-account surface.
Mutating tools require an idempotency key, so a retried call replays the original result instead of duplicating work.
The connector and all its tools, Answer Radar included, come with the Compete plan at no additional cost.
60 requests per minute per user
Four steps, and every tool arrives at once.
In Claude.ai, go to Settings, then Connectors, then Add custom connector. Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf all have an equivalent screen.
Use https://mcp.linkeddit.com/mcp as the connector URL. There is nothing to install and no server to host.
When Claude asks for an OAuth Client ID, enter linkeddit-mcp-claude and leave the Client Secret blank. Linkeddit uses pre-registered public PKCE clients rather than dynamic registration, so this one field replaces the whole API-key step.
Sign in with your Linkeddit account in the browser when prompted. After that, ask something like "Where are AI answer engines recommending competitors instead of us?" or "What did our top competitor change this week?" and Claude calls the right tools itself.
Detailed guides: Claude connector MCP setup and the full setup blog post.
A Claude Connector is a remote MCP (Model Context Protocol) server that gives Claude access to external tools and data. Linkeddit's connector exposes 34 tools covering AI-search visibility, competitor intelligence, keyword research, and Search Console, so Claude can answer from your own market data instead of guessing.
In Claude.ai go to Settings, Connectors, Add custom connector, and paste https://mcp.linkeddit.com/mcp. When prompted for an OAuth Client ID enter linkeddit-mcp-claude and leave the Client Secret blank. Authorize once in the browser with your Linkeddit account and every tool is available in the conversation. There are no API keys to generate or headers to paste.
No. The connector authenticates with OAuth 2.1 and PKCE, so authorization happens once in your browser and there is nothing to store or rotate.
Clients with native remote MCP support take the URL https://mcp.linkeddit.com/mcp directly. Clients without it bridge the OAuth flow with mcp-remote. Pass the pre-registered client id with --static-oauth-client-info '{"client_id":"linkeddit-mcp-claude"}'. Claude Code users can run: claude mcp add --transport http linkeddit https://mcp.linkeddit.com/mcp
Any MCP client. That includes Claude.ai on the web, Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf. ChatGPT's connector support works the same way.
The connector is included with the Compete plan, which unlocks every tool including Answer Radar, and allows 60 requests per minute per user.
Setup takes under two minutes: paste the URL, paste the Client ID, authorize once. No keys to generate, store, or rotate.