Setting up an existing AI client? See Paperzilla plugin setup for Claude, ChatGPT, Codex, and OpenClaw.
Configure the transport and scopes
- Point your MCP client at
https://paperzilla.ai/api/mcpand select Streamable HTTP. Let the SDK negotiate the MCP version and follow the server’s OAuth discovery metadata. - Request
catalog:readto check account access and read public digests. Addprojects:readif the agent reads the user’s own project feeds. Addoffline_accessif your agent needs to refresh the connection between runs. - Configure your SDK’s OAuth callback. For a public client, use authorization code with PKCE S256, a redirect URI that matches the registration, and
token_endpoint_auth_methodset tonone. Send the advertised resourcehttps://paperzilla.ai/api/mcpon both the authorization request and the code exchange. See the Paperzilla OAuth reference for registration options and metadata URLs.
Authorize the account
- Start the OAuth flow from your client and open the authorization URL in the user’s browser. The user signs in to Paperzilla and reviews the requested access.
- On return to your callback, let the SDK verify the OAuth state and exchange the code. Store credentials securely with the corresponding user connection. Send the OAuth access token in the Authorization header on MCP requests.
- If you requested refresh access, serialize refreshes for each connection and save the replacement refresh token after each successful exchange. If the user revokes access, start a new browser authorization before resuming reads.
Verify access before enabling the agent
- Use your SDK to list tools and call
account_statuswith an empty arguments object. Check the granted scopes. An account can read public digests before it owns any projects. - Call
public_digests_searchwith the following arguments to try a public read. Use the returned series ID withpublic_digest_issues_listand open an issue from that list withpublic_digest_get. See the MCP tool reference.
- If you requested private feed access, call
projects_listand use a returnedproject_idwithfeed_get. If there are more results, use the returnednext_offsetto request the next page. If the account has no project, use the setup URL fromaccount_status.
Diagnose connection issues
- If discovery or authorization fails, compare the same URL and scopes in MCP Inspector. Check your callback URL and that your SDK sends the resource during authorization and code exchange.
- If a tool needs a scope you didn’t request, start a new authorization with that scope. Refreshing the existing token preserves the existing grant.
- If you’re testing an unattended run, authorize in the browser first. Run it with the saved connection and confirm it can refresh before relying on a schedule. You can revoke a test connection from Connect AI clients.