← All updates

Connect makesPDF to Claude with OAuth — no API key

claude.ai, Claude Desktop connectors and Claude Code can now add makesPDF by URL and sign in with OAuth. Add the connector, approve access once, and the PDF tools work — no API key, no Request-headers beta.

mcpoauthclaudeconnectors

You can now add makesPDF as a custom connector in claude.ai and Claude Desktop, or connect Claude Code, with nothing but the server URL. There is no API key to paste and no Request-headers beta to wait for. Point the connector at https://makespdf.com/api/v1/mcp, leave the client ID, secret and headers fields empty, and the first tool call starts a normal sign-in.

Claude opens a makesPDF consent page the first time it needs to render or validate something. The page names the requesting client by the host of its client_id URL — not a name the client chose for itself — and shows where your browser will return before you approve.

Once you approve, the connection stays live while you use it: the access token lasts an hour and refreshes automatically, and a connection that sits unused for 30 days lapses and has to be re-added. There is no connected-apps list to review these yet — removing the connector in Claude and signing out of makesPDF ends your use of it, and the tokens themselves expire within 30 days of the last use.

OAuth access tokens are deliberately narrow. Each one is bound to makesPDF's MCP URL and is accepted only on /api/v1/mcp; presenting it to the REST render endpoints is rejected. Billing, rate limits and usage rows are attributed to the account that signed in, and refresh tokens rotate on each use. API keys keep working exactly as before, so existing Cursor, VS Code and scripting setups need no changes.

Claude Code can use the same flow:

claude mcp add --transport http makespdf https://makespdf.com/api/v1/mcp
# then, inside Claude Code:
/mcp   # choose makespdf -> Authenticate -> approve in the browser

Full client steps, including when to use an API key instead, are on /docs/mcp.