Paperwork MCP connector
The Paperwork MCP connector gives an MCP client one tool for each Paperwork task.
Each tool calls one or more /v1 routes of the Paperwork API with your credential.
This connector is different from the MCP server at the host root. The root server exposes the full API through two Code Mode tools. The connector exposes fixed tools with a clear read or write type.
URL
The connector lives at https://mcp.cloudraker.com/paperwork.
OAuth discovery for this URL is at https://mcp.cloudraker.com/.well-known/oauth-protected-resource/paperwork.
Add the connector in Claude
- In Claude, open Settings > Connectors.
- Select Add custom connector, or find CloudRaker Paperwork in the connector directory.
- Enter the URL
https://mcp.cloudraker.com/paperworkfor a custom connector. - Select Connect, then sign in with your CloudRaker account.
Authentication
The connector accepts two Bearer credentials:
- CloudRaker sign-in (OAuth 2.0). Claude runs the sign-in flow. The token is valid only for the
/paperworkURL. - Organization API key. Other MCP clients can send an organization API key in the
Authorizationheader.
The /v1 API accepts an OAuth sign-in only from an organization administrator.
A member who is not an administrator gets 403 on every tool.
Use an organization API key for a member account.
The connector does not keep your credential. Tool results never contain it.
Tools
A read tool only reads data. A write tool creates a file, starts a run or spends credits.
Runs
The parse, extract, classify, redact and fill tools start a run.
Each tool waits up to 25 seconds for the result by default.
If the run is not done, the tool returns the run id and status. get_run returns the result.
A failed run is not a tool error. The run result has the status failed and an error code.
Errors
A tool error contains the HTTP status, the error code, the message and the request ID. Send the request ID to support when you report a problem. See Errors for the codes.
Credits
Write tools that run a capability use credits, the same as the /v1 routes.
A tool returns 402 when the organization has no credits or the plan does not include the capability.
Read tools do not use credits.
Privacy and support
The CloudRaker privacy policy applies to all data that the connector reads or writes. For help, send an email to support@cloudraker.com.