> This page is for RakeSign.

> 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.

# MCP connector

The RakeSign MCP connector gives an MCP client one tool for each signing task.
Each tool calls one or more `/v1/signing` routes with your credential.

## URL

The connector lives at **`https://mcp.cloudraker.com/sign`**.
OAuth discovery for this URL is at `https://mcp.cloudraker.com/.well-known/oauth-protected-resource/sign`.

## Add the connector in Claude

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

With a sign-in, you must be an active member of the organization.
The tools then have the same access as you have in the RakeSign app.
With a key, the tools have the team and scopes of that integration.

```bash
claude mcp add --transport http rakesign https://mcp.cloudraker.com/sign \
  --header "Authorization: Bearer $RAKESIGN_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 or changes a document, or sends email.

| Tool                  | Type  | What it does                                                                                                                       |
| --------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `list_templates`      | Read  | Lists the signing templates with their recipient roles.                                                                            |
| `list_documents`      | Read  | Lists signature documents with their status.                                                                                       |
| `get_document`        | Read  | Returns one document with its recipients and status.                                                                               |
| `get_envelope_status` | Read  | Returns the document status, each recipient status, the next pending recipients and the last 10 audit events.                      |
| `create_document`     | Write | Creates a draft from a template or from a file (PDF, DOCX, PPTX or XLSX, 20 MB maximum). It does not send the draft.               |
| `send_document`       | Write | Sends a draft for signature. RakeSign sends an email to each recipient.                                                            |
| `remind_signers`      | Write | Sends a new invitation email to the pending recipients of the current stage, or to one recipient. The previous link stops working. |
| `void_document`       | Write | Cancels a sent or draft document. All signing links stop working.                                                                  |
| `download_signed_pdf` | Read  | Returns the signed PDF of a completed document (10 MB maximum).                                                                    |

### Email to recipients

`send_document` and `remind_signers` send email to real people.
`void_document` sends no email: it stops the signing links and fires the `document.cancelled` webhook.
These tools are marked destructive, so Claude asks for confirmation unless you allowed the tool permanently.
Make sure that the document and the recipients are correct before you confirm.

### Signed PDF

`download_signed_pdf` works only when the document status is `completed`.
For a larger file, download the PDF in the RakeSign app at `https://sign.cloudraker.com`.

### Errors

A tool error contains the HTTP status, the message and the request ID.
Most RakeSign `4xx` errors share the code `bad_request`, so read the status and the message.
Send the request ID to support when you report a problem.

## Credits

`send_document` uses credits.
It returns `402` when the organization has no credits or the plan does not include e-signature.
The other 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

#### [Document workflow](/rakesign/developers/documents)

The document lifecycle and statuses.

#### [Paperwork MCP connector](/paperwork/developers/mcp-paperwork)

Parse, extract and fill documents from Claude.