Paperpin DocsMCP connection
Connect OAuth-authorized MCP clients to Paperpin's remote server for secure AI access to monitoring data.
Paperpin exposes one canonical stateless Streamable HTTP MCP server:
https://paperpin.io/api/mcpAuthenticate with OAuth
Enter the endpoint in an OAuth-capable remote MCP client. The client discovers Paperpin's authorization server, opens the Paperpin consent screen, and uses OAuth 2.1 Authorization Code with S256 PKCE. Do not create or paste a Paperpin API key into an MCP client.
Access tokens are short lived and restricted to the resource and scopes you approve. Refresh tokens are issued only when the client requests and you approve offline_access.
Paperpin API keys beginning with pp_ are for the REST API. Pre-migration keys may work temporarily during the announced migration window, but newly created keys never authorize MCP access.
Permissions
The initial connection requests read access. A client can request additional permission when you invoke a protected tool:
| Scope | Permission |
|---|---|
paperpin:read | Read groups, monitors, change events, insights, and trends |
paperpin:groups:write | Create and rename groups |
paperpin:monitors:control | Run, pause, and resume monitors |
paperpin:delete | Delete groups and monitors |
Paperpin returns an OAuth insufficient_scope challenge when a tool needs permission the client does not have. Compatible clients can request the additional scope and retry after approval.
Monitor runs are single-resource operations. PaperPin exposes run_monitor and does not provide a group-run or batch-run tool.
Revoke access
Open Developer Access to review connected application names, granted scopes, authorization time, and last use. Revoking an application immediately invalidates its active access and refresh tokens.
MCP authorization is resolved from the verified OAuth identity to the Paperpin workspace on the server. Client-provided tenant identifiers and user metadata are never used to authorize tools.
See MCP tools for the complete tool surface.