Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth 2.1 can use Linnia.

Setting	Value
Server URL	https://mcp.linnia.ai/mcp
Transport	Streamable HTTP
Authorization	OAuth 2.1, authorization code with PKCE
Client registration	Dynamic (RFC 7591). Leave client ID and secret empty.
Authorization server metadata	https://mcp.linnia.ai/.well-known/oauth-authorization-server
Protected resource metadata	https://mcp.linnia.ai/.well-known/oauth-protected-resource/mcp
Scopes	read write:messages write:network write:content write:notes

Use OAuth, not an API key: a request to /mcp without a valid access token gets 401 with a WWW-Authenticate header pointing at the protected resource metadata, which is how clients discover where to sign in.

Tokens. Access tokens last 8 hours; refresh tokens last 30 days and rotate on use. Clients can revoke tokens at the server’s revocation endpoint (listed in the metadata).

Sign-in. The user signs in with their Linnia email and password (plus two-factor code if enabled) and, when the workspace has several LinkedIn accounts, picks which ones the client may use.

Waiting for jobs. get_job waits as long as the client usually allows. Clients whose name contains Claude Code, Cursor, Codex, VS Code or Windsurf get about 590 seconds; Claude about 170; ChatGPT or OpenAI about 45; anything else about 55.