Connect your client
Authentication & scopes
How the Linkeddit connector authenticates over OAuth 2.1 and what each scope grants.
OAuth 2.1, no API keys
The connector authenticates with OAuth 2.1 bearer tokens only. There are no API keys or custom headers to configure. Your MCP client discovers how to authenticate from the connector's protected-resource metadata and runs the standard authorization-code + PKCE flow in your browser.
- Protected-resource metadata is published at https://mcp.linkeddit.com/.well-known/oauth-protected-resource, pointing to the authorization server.
- The authorization server is the Linkeddit app itself (linkeddit.com). You sign in with your normal Linkeddit account.
- Tokens are audience-bound to https://mcp.linkeddit.com/mcp; a token minted for anything else is rejected.
- Client registration is pre-registration, not dynamic (RFC 7591). Clients that can auto-register do so transparently; clients that can't (Claude.ai) must be given the public Client ID
linkeddit-mcp-claude. There is no client secret (PKCE only).
OAuth Client ID (Claude.ai and other clients)
Linkeddit does not support automatic (dynamic) client registration, so any client that can't self-register needs a pre-registered Client ID. It is a public, PKCE-only client. There is no client secret.
linkeddit-mcp-claudetextlinkeddit-mcp-claude, and leave the Client Secret blank. Clients that register automatically skip this step.Scopes
Scopes gate what an assistant can do with each tool. You don't set them by hand: when you authorize on the Compete plan, your token is granted the full set below, so there is nothing to configure.
| Scope | Grants |
|---|---|
| answer:read | Read Answer Radar projects, prompts, gaps, results, and audit runs, plus Search rankings and Search Console queries |
| answer:write | Create/configure Answer Radar projects, update prompts, save fixes, change tracked keywords, and save articles |
| answer:run | Run audits, start re-verifications, and run keyword research (these incur spend) |
| keywords:read | Keyword autocomplete, SERP research, and your keyword research jobs |
| compete:read | Competitor briefs, signals, reviews, monitors, and page changes |
Entitlement, idempotency & rate limits
- Every connector tool requires the Compete plan; on any other plan calls are refused with
not_entitled. Compete unlocks the entire toolset. - Mutating tools take an
idempotency_key(1-200 chars). Re-sending the same key replays the prior result instead of doing the work twice. - Requests are rate limited per authenticated user (default 60 per minute). Audits also consume budget: call
answer_audit_runwithout confirm first to get the estimate.
Frequently asked questions
How does the Linkeddit connector authenticate?+
With OAuth 2.1 bearer tokens and the authorization-code plus PKCE flow, run in your browser. There are no API keys or custom headers.
Why does Claude.ai ask for an OAuth Client ID?+
Linkeddit does not support dynamic client registration, so clients that cannot self-register need the pre-registered public Client ID linkeddit-mcp-claude. There is no client secret.
Which scopes does the connector use?+
answer:read, answer:write and answer:run for Answer Radar, keywords:read for keyword research, and compete:read for competitor intelligence. Authorizing on the Compete plan grants the full set.
Can a retried call run twice?+
No. Mutating tools take an idempotency_key, and re-sending the same key replays the earlier result instead of doing the work again.