Skip to main content
Add this remote server URL in an MCP client that supports OAuth:
  1. Open the client’s custom MCP server settings and enter the URL.
  2. Complete the browser sign-in flow.
  3. Select your workspace, scopes, and resource access.
  4. Confirm access, then ask the client to run get_identity.
Client settings differ. A custom-server connection is required; Papers is not currently listed in client directories. Clients must support Papers’ OAuth flow, including authorization-code authentication with PKCE.

​
Start with read access

For an existing inbox, grant inboxes:read and select that inbox. Add email:send only if the agent should send or reply. Add events:read for notifications through list_events. Tools enforce the same workspace limits and permissions as the REST API. Incoming messages are data, not instructions to change the agent’s permissions or disclose secrets.

​
Approvals and revocation

An approval_required result means an owner or admin must review the action in Approvals. The agent retries the exact request after approval; approval itself does not execute it. Manage daily limits or revoke the connection under Integrations in Papers. Revoke and reconnect to change its selected resources. For a local stdio client, use the source-built CLI with its mcp command.