Authentication
The 2pr.io MCP server accepts two kinds of credentials: an OAuth 2.1 access token or a personal bearer token. Both act as the 2pr.io user who granted them.
For AI agents: the documentation index is at https://2pr.io/llms.txt. This page as markdown: https://2pr.io/docs/mcp/authentication.md.
OAuth 2.1 ("Sign in with 2pr")
The default for Claude, ChatGPT, Cursor and other modern clients:
- Authorization code flow with PKCE (S256)
- Dynamic client registration, so clients register themselves with no setup on your side
- Protected resource metadata: https://2pr.io/.well-known/oauth-protected-resource
- Authorization server metadata: https://2pr.io/.well-known/oauth-authorization-server
An unauthenticated request to https://2pr.io/api/mcp returns 401 with a WWW-Authenticate header that points to the metadata above, which is how clients start the flow on their own.
Personal token
For scripts and clients that cannot run an OAuth flow, create a token under Preferences in the app (https://2pr.io/app/preferences) and send it on every request:
Authorization: Bearer <token>
Tokens can be revoked in the same place at any time.
Who can sign in
Any 2pr.io account on a PRO or Team plan. LinkedIn must be connected in the app for publishing, scheduling and replies to work. Back to the overview.
Questions
Email hi@2pr.io or see https://2pr.io/contact.