> This page is for Paperwork API, version v1 (default).
> For other versions, use one of these documentation indexes:
> - v1 (default): https://docs.cloudraker.com/paperwork/v1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# 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](/paperwork/developers/mcp) 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

1. In Claude, open **Settings > Connectors**.
2. Select **Add custom connector**, or find **CloudRaker Paperwork** in the connector directory.
3. Enter the URL `https://mcp.cloudraker.com/paperwork` for a custom connector.
4. 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 `/paperwork` URL.
* **Organization API key.** Other MCP clients can send an [organization API key](/paperwork/developers/authentication) in the `Authorization` header.

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.

```bash
claude mcp add --transport http cloudraker-paperwork https://mcp.cloudraker.com/paperwork \
  --header "Authorization: Bearer $RAKERONE_API_KEY"
```

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.

| Tool                     | Type  | What it does                                                                                                                                                              |
| ------------------------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `upload_file`            | Write | Adds a file from a public URL or from base64 content (10 MB maximum). Returns the file object. CloudRaker parses the file and uses credits unless `processing` is `none`. |
| `list_files`             | Read  | Lists the files in the organization API workspace, newest first.                                                                                                          |
| `get_file`               | Read  | Returns one file with its status and signed links when it is ready.                                                                                                       |
| `parse_document`         | Write | Parses a file to Markdown and JSON. Returns links to the output.                                                                                                          |
| `extract_data`           | Write | Extracts structured data from one or more files, with an optional JSON Schema.                                                                                            |
| `classify_document`      | Write | Classifies one or more files, or their pages, into 2 to 50 classes.                                                                                                       |
| `compose_document`       | Write | Renders a PDF from a saved compose template and a data object.                                                                                                            |
| `list_compose_templates` | Read  | Lists the saved compose templates of the organization.                                                                                                                    |
| `redact_document`        | Write | Makes a redacted copy of a document or recording. The original file does not change.                                                                                      |
| `fill_form`              | Write | Fills a PDF form from field values or from source files.                                                                                                                  |
| `inspect_form`           | Read  | Lists the fillable fields of a PDF form. The field names are the keys that `fill_form` accepts.                                                                           |
| `redline_document`       | Write | Applies a list of tracked edits to a Word document and returns the new file.                                                                                              |
| `get_run`                | Read  | Returns the status and result of a run.                                                                                                                                   |
| `list_runs`              | Read  | Lists recent runs.                                                                                                                                                        |

### 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](/paperwork/developers/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](https://cloudraker.com/legal/privacy) applies to all data that the connector reads or writes.
For help, send an email to [support@cloudraker.com](mailto:support@cloudraker.com).

## Where to go next

#### [RakeSign MCP connector](/rakesign/developers/mcp)

Send documents for signature from Claude.

#### [Runs](/paperwork/developers/runs)

The run model, statuses and polling.