> ## Documentation Index
> Fetch the complete documentation index at: https://docurise.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect AI apps (MCP)

> Connect DocuRise to Claude, ChatGPT and other AI apps with the MCP server

DocuRise has an [MCP](https://modelcontextprotocol.io) server. Add it to an AI app such as Claude or
ChatGPT, sign in with your normal DocuRise login, and the app can use a small set of DocuRise tools
on your behalf. You never create or paste an API key.

> [!NOTE]
>
> The MCP server is a **preview**. It is available only to some accounts, and only on a plan that
> includes it. Tools, names and behavior can still change.

## Before you start

* Sign in to DocuRise in the same browser you will use for the AI app. The approval page asks you to
  sign in if you are not.
* MCP is available only to some accounts, on a plan that includes it (see the note
  above). If MCP isn't available for your account, the approval page tells you and nothing is connected.
* You do not need to install anything for Claude or ChatGPT on the web. Claude Code runs in a
  terminal and needs to be installed first.

## Server URL

This is the one address every AI app needs. Use the copy button at the top right of the box.

```
https://docurise.io/api/mcp
```

Paste it exactly as shown, with nothing added at the end. The server uses the MCP Streamable HTTP
transport, signs you in with OAuth, and keeps no session between requests.

## Add DocuRise to your AI app

Pick your app below. The steps differ a little, but the idea is always the same:

1. Add DocuRise to the app as a custom connector or remote MCP server, using the server URL.
2. A DocuRise page opens. Sign in if asked, then choose **Approve**.
3. Back in the app, DocuRise is connected.

App menus change from time to time. If a name below differs from what you see, look for the option to
add a connector or an MCP server.

### Claude

Works in claude.ai and the Claude desktop app.

**1. Open the connector settings**

In the left sidebar, open **Customize** and choose **Connectors**. In older versions of the
app this is **Settings → Connectors**.

**2. Add a custom connector**

Click **Add** at the top right, then **Add custom connector**. A small window opens with two
fields.

**3. Fill in the two fields**

In **Name**, type `DocuRise`. In **MCP server URL**, paste this address:

```
https://docurise.io/api/mcp
```

Then click **Continue**. If Claude lists the new connector with a **Connect** button, click it.

**4. Approve on the DocuRise page**

A DocuRise page opens in your browser. Sign in if asked. You will see your account, the app that
is asking, and a choice between **Read only** and **Read and write**. **Read only** is already
selected, which is the safe choice, so you can simply click **Approve**. To let Claude create
things later, connect again and choose read and write.

**5. Check Claude's tool permissions**

After you approve, Claude shows the DocuRise connector with a **Tool permissions** section:
"Choose when Claude can use these tools". The tools are listed in two groups, **read-only tools**
and **write/delete tools**, and each tool has three options: always allow, needs approval, or
block.

**You don't need to change anything here.** Every default works, so leave all of them as they
are and close the window. These settings only control how often Claude stops to ask you first,
and you can come back and change them whenever you like. Tools that need write access are only
listed if you approved **Read and write**.

To try it, start a new chat and ask: *"Use DocuRise to list my five newest documents."* If Claude
asks whether it can use a DocuRise tool, allow it.

### ChatGPT

**1. Open the plugin settings**

Open **Plugins**, choose **Add** at the top right, then **Create custom MCP server**.

**2. Fill in the form**

In the name field, type `DocuRise`. In the server URL field, paste this address:

```
https://docurise.io/api/mcp
```

Keep authentication as **OAuth**. ChatGPT reads the OAuth settings from DocuRise on its own, so
leave the client ID and secret empty.

**3. Create it and approve**

Tick the confirmation box and create the server. A DocuRise page opens: sign in if asked and
choose **Approve**. **Read only** is already selected and works for most people.

**4. Use it in a chat**

In a chat, type `@DocuRise` to use it, for example *"@DocuRise list my five newest documents"*.

### Claude Code

Claude Code is Claude in your terminal. You need it installed first.

**1. Add the server**

Open a terminal, paste this command, and press Enter:

```bash theme={null}
claude mcp add --transport http docurise https://docurise.io/api/mcp
```

**2. Start Claude Code and sign in**

Run `claude`. Inside Claude Code, type `/mcp`, select `docurise`, and follow the sign-in link.
A DocuRise page opens in your browser: sign in if asked and choose **Approve**. **Read only** is
already selected.

**3. Check that it worked**

Run `/mcp` again. `docurise` should show as connected. You can also run `claude mcp list` in a
normal terminal.

### Other apps

In any app that supports remote MCP servers with OAuth, add a remote MCP server (HTTP) and enter
this server URL when it asks for one:

```
https://docurise.io/api/mcp
```

Then approve the connection on the DocuRise page that opens.

* Verified so far: Claude, ChatGPT and Claude Code.
* Cursor is not supported yet.

## What you approve

Every connection goes through one DocuRise approval page, whichever app you use. It shows your
account, the app that is asking, and the access level. If you are not sure what to pick, leave the
preselected **Read only** and click **Approve**.

| Access | What the app can do |
| - | - |
| Read | Use read-only tools. This is preselected. |
| Read and write | Also use tools that create or change things in your account. |

The app only sees the tools your access level allows.

To switch an existing connection between read only and read and write, connect the app again and
choose the other level. The access level of a connection can't be changed after it is created.

## Tools

| Tool | Access | What it does |
| - | - | - |
| `docurise_get_account` | Any | Reports this connection's access level, its permissions, and whether your plan includes MCP. Never returns credentials. |
| `docurise_list_documents` | Read | Lists your documents, newest first, optionally by status (live, draft, inactive, expired). |
| `docurise_get_document` | Read | Shows one document: status, expiry, the version to send back when editing it, and whether it is password-protected, requires an email, or has an allowlist. Never returns passwords or the lists of allowed viewers. |
| `docurise_get_document_analytics` | Read | Views, unique visitors and leads for one document or your whole account, a trend over time (per day or week), a comparison by traffic source, a form funnel, or your top documents. On account-wide views, unique visitors and leads are each document's figures added up, so they are not unique across the account. |
| `docurise_list_library` | Read | Lists your folders, tags, groups, products or the approved Kakao message templates you can use in an automation. |
| `docurise_list_email` | Read | Lists your email broadcasts and automations, or shows one broadcast's delivered, opened, clicked and bounced totals. Never returns email bodies or recipients. |
| `docurise_list_instagram_rules` | Read | Lists your Instagram comment-to-DM rules with their status, keywords, schedule and send counts, plus the links each DM sends: the web address (without anything after a `?` or `#`) and, when it opens one of your own documents, that document's title and status. Never returns message text or button text. |
| `docurise_list_group_conditions` | Read | Lists the rules a group can be built from (for example "has this tag", "viewed this document in the last 30 days", "bought this product"), with the options each takes and where to find the ids it needs. It is the same for every account and reads none of your data. It also states which operator and id shapes are refused in which list. Custom-field rules are not available yet. |
| `docurise_preview_group` | Read | Counts how many of your contacts a set of group rules would match, without saving anything, so the app can show you the size before it creates the group. Returns only the number, never names, emails or other contact details. |
| `docurise_check_connections` | Read | Health check of your own setup: active email automations whose trigger document was deleted, Instagram DM rules linking to a deleted document of yours, and email automations that use the recipient's name when the form does not collect one. Reports ids and names only, never message text or links. |
| `docurise_create_document` | Read and write | Creates an email-collection form or a post and publishes it right away: it is live as soon as it is created, and the app gets back the public link and a dashboard link where you can check it, edit it or switch it off. Create one only when you want it public. It counts toward your published-document limit; when there is no room, nothing is created. For a form, the app must say whether it shows the marketing-consent checkbox, which a follow-up automation relies on (it emails contacts who have given marketing consent). For a form, the app can also write the intro text above the questions with formatting (bold, underline, highlight, colors, heading sizes, lists and links); the form's short description is only used for link previews and is not shown on the form. For a post, the app sends either formatted text (available on every account) or the page as HTML (up to 200,000 characters, only on accounts that have HTML posts). Both are cleaned when they are saved (scripts, forms and iframes are removed), so open the page and check it. A post is open to everyone unless you ask for a gate: the app can turn on the email gate (and, with it, email verification, business emails only, or a blurred preview) when you tell it to; a form always asks for the email. Gates are set when the post is created; to change them later, use the document's settings in the dashboard. The public link can be used in an Instagram DM rule button. Never returns submitted data or the post's content. The same request twice creates one document. |
| `docurise_update_document` | Read and write | Edits the content of one of your forms or HTML posts and saves it right away: the title and description, a post's HTML, a form's formatted intro text, a form's name, company and phone fields and its marketing-consent checkbox, and new questions for a form. Questions can only be added, after the existing ones (up to 10 extra in total); an AI app cannot reword, reorder or remove an existing question, so you do that in the dashboard. On a live document, visitors see the change immediately. The app has to read the document first and send back the version it read; if you saved in the dashboard in the meantime, the edit is refused so it cannot overwrite your work. It also refuses, tells you why and sends you to the dashboard to make the change yourself, when an automation or a Kakao lead notification is set up on the document (a new title or description is still allowed, a new intro text is not), when a form takes payment (its fields, questions and marketing-consent checkbox), when a form's saved layout cannot be read safely by an AI app, when a post was written in the editor rather than as HTML, or when a post has videos and you change its HTML (replacing it would detach them; its title and description can still change). Adding more questions than the form has room for is refused too. Never returns the post's HTML or the form's questions. |
| `docurise_create_automation_draft` | Read and write | Creates the follow-up message for one of your forms: when someone submits it, the app sends an email it wrote, or a Kakao alimtalk from one of your approved templates, after the wait you choose. For a Kakao message the app lists your approved templates and you pick the one to use; it does not choose for you. It is always a draft and never turns on: nothing is sent until you open the returned link, review the message and turn it on yourself in the dashboard. The app gives you the link and the steps in order, and explains what will happen once it is on. A form that is still a draft (made in the dashboard) must be published first, and one that is switched off must be switched on, before anyone can submit it. It sends only to contacts who have given marketing consent, which ticking the form's marketing-consent checkbox records, so new contacts from a form without that checkbox are not messaged, and the app is told to warn you. The app decides this for each automation: a transactional message, such as a confirmation or the delivery of what the person asked for, is created with "Require marketing consent" off, and the message then goes to everyone who submits the form (unsubscribed and bounced contacts, and Kakao opt-outs, are still skipped); the app is told to say so and never to do this for promotion. A Kakao message goes to a phone number, so the form needs a phone field; the app is told to warn you when it has none. Turning a Kakao automation on needs Kakao credits; creating the draft costs nothing. Never returns submitted data, message recipients or the text of a Kakao message. The same request twice creates one automation. An account can hold at most 50 automations that are not turned on. [How to review and turn it on](https://docurise.io/docs/mcp-review-and-activate.md). |
| `docurise_create_group` | Read and write | Creates a group: a named list of contacts defined by rules, such as everyone tagged "vip" who viewed a document in the last 30 days. The group keeps itself up to date as contacts change. Creating it sends nothing to anyone and changes no contact; you use it later as the audience of an email or an automation in the dashboard. A rule that names a tag, document, folder, product or another group must name one of yours, and a wrong rule is refused with the reason. A few rule shapes are refused because they would silently drop contacts: in the exclude list, `is` for location or bounce status, and product- or form-scoped purchase conditions; the refusal says what to use instead. A very heavy rule can time out after about 10 seconds while the app counts it; the app is told to simplify the rule or retry. Repeating the same request does not create a second group. Returns a link to the group page. An account can have up to 100 groups this way. It cannot edit or delete groups. |
| `docurise_create_instagram_rule` | Read and write | Creates your next-post Instagram comment-to-DM rule, always paused: nothing is sent until you turn it on in the dashboard. Needs at least 3 different comment replies, or replies turned off. Returns a link to the rule, never its message text. Repeating the same request does not create a second rule. |
| `docurise_update_instagram_rule` | Read and write | Pauses your next-post rule. It can only pause: it cannot turn a rule on or change its messages. Pausing a rule that is already paused is fine. |
| `docurise_create_tag` | Read and write | Creates one tag by name, for example `webinar-oct`. A tag is a label you later put on contacts and use in groups and automations; creating one sends nothing and changes no group. If you already have a tag with the same name (ignoring letter case and surrounding spaces) nothing new is created and the existing tag is returned. It does not put the tag on any contact. |

Text that you or your visitors wrote (titles, names, keywords) is returned as data, never as instructions.
Read tools only read. Tools that need read and write access create things in your account and give you a dashboard link to review them. Instagram rules and email and Kakao automations are created paused and send nothing until you turn them on; the one tool that publishes is `docurise_create_document`, which makes a form or post live at once. `docurise_update_document` edits a form or post you already have and saves the change at once, so on a live document visitors see it straight away; it never changes whether a document is published. `docurise_create_group` saves a group of contacts; a group sends nothing on its own. No tool sends anything or turns a rule or automation on. More tools will be added over time; existing tool names will not change.

## Limits

Each account can make up to 60 MCP requests per minute and 5,000 per day. These limits are separate
from the [API rate limit](https://docurise.io/docs/errors.md#rate-limits), so AI apps and API keys do not use up each other's
requests. A request over the limit gets a `429` with a `Retry-After` header; wait that long and retry.

An account can also have up to 20 MCP requests running at the same moment. A busy AI app stays well
under this, so you will only see it if an app sends a very large number of calls at once; the extra
requests get a `429` with `Retry-After: 1`, and the app can retry after that pause. A refused request
still counts toward the per-minute and daily limits above.

## Revoke a connection

Open **Settings → Developers** in the dashboard. The connected AI apps list shows every approval
with its access level, when it was created, and when it was last used. Choose **Revoke** on a
connection. It stops working on the app's next request, and the app has to ask you to sign in again.

You also get an email each time a new app is connected. If you did not start that connection, revoke it.

## Troubleshooting

* **The app cannot connect or shows an error after sign-in.** Check that you copied the URL exactly,
  with no trailing path, and that MCP is available for your account and plan.
* **A tool is missing.** Your approval may be read-only. Connect again and choose read and write. In Claude, also check that the tool is not set to block under
  **Tool permissions**.
* **Claude keeps asking before it uses a tool.** That is the "needs approval" option in Claude's tool
  permissions. Switch a tool to always allow if you no longer want to be asked.
* **It stopped working.** The connection may have been revoked, expired, or your plan may no longer
  include MCP. Reconnect from the app.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.