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

# Connect ChatGPT and Claude

> Connect ClearPolicy to ChatGPT or Claude so you can draft and publish policies, send document requests, check status, and send reminders using plain language.

export const ChatGptInstallCard = ({href, title, description, cta}) => <div className="not-prose my-4 w-full">
		<a href={href} target="_blank" rel="noopener noreferrer" className="group flex w-full items-start gap-4 rounded-2xl border border-gray-200 p-4 no-underline transition-colors hover:border-gray-300 dark:border-white/10 dark:hover:border-white/20">
			<img src="/images/chatgpt-icon.svg" alt="" width={40} height={40} className="mt-0.5 h-10 w-10 shrink-0" />
			<div className="flex min-w-0 flex-1 flex-col gap-2">
				<div className="block text-base font-semibold leading-snug text-gray-900 group-hover:underline dark:text-white">
					{title}
				</div>
				<div className="block text-sm leading-relaxed text-gray-600 dark:text-white/70">
					{description}
				</div>
				<div className="block text-sm font-medium leading-snug text-emerald-600 dark:text-emerald-400">
					{cta} →
				</div>
			</div>
		</a>
	</div>;

Use ChatGPT or Claude to work with your ClearPolicy organization in everyday language. Draft or revise a policy, ask who still needs to sign, send a document to someone, or send reminders — without clicking through the app.

ClearPolicy connects through a secure industry standard called **MCP** (Model Context Protocol). You do not need to understand the technical details. In most cases, you add ClearPolicy inside ChatGPT or Claude, sign in when prompted, and start asking questions.

<Note>
  This is a **personal connection**. Each team member connects their own ChatGPT or Claude account. Access applies to whichever organization you have selected in ClearPolicy when you authorize the connection.
</Note>

## What you can do

Once ClearPolicy is connected, you can ask your AI assistant to:

* Create a new document as a draft, and describe what the policy should say
* Review or update a draft revision, then publish it when you are ready
* Send a document for electronic signature
* Check who still has a pending request
* Send reminders for outstanding requests
* Add a person, then send them a document in the same conversation
* Check whether a specific person has completed a document
* Work with groups (list groups, add a person to a group)
* Review compliance across documents in your organization

<h2 id="chatgpt">
  Connect ChatGPT
</h2>

The easiest way to connect is through the ChatGPT Apps library:

<ChatGptInstallCard href="https://chatgpt.com/apps/clearpolicy/asdk_app_69eee2d237b881918747780ab313427d?utm_source=clearpolicy&utm_medium=docs&utm_campaign=docs_chatgpt_app&utm_content=mcp_install_card" title="Install in ChatGPT" description="Install ClearPolicy from the ChatGPT Apps library, then sign in to connect your organization." cta="Open in ChatGPT Apps library" />

1. Open the **ClearPolicy** listing in the ChatGPT Apps library (link above).
2. Install the app and sign in to ClearPolicy when prompted to approve access.
3. Return to **Settings → AI assistants** in ClearPolicy to confirm you are connected.

### Manual MCP setup (alternative)

If ClearPolicy does not appear in your Apps library, or your plan does not support Apps yet, add a custom MCP connector:

1. Open **ChatGPT** and go to **Settings**.
2. Open **Apps & Connectors** (some plans require **Developer Mode** first).
3. Add a custom MCP connector.
4. When ChatGPT asks for connection details, use the values in [Connection details](#connection-details) below.
5. Save the connector. ChatGPT opens ClearPolicy so you can sign in and approve access.
6. Return to **Settings → AI assistants** in ClearPolicy to confirm you are connected.

<Note>
  The exact labels in ChatGPT can vary by plan. If you do not see **Apps & Connectors**, check ChatGPT’s help for adding a custom MCP connector.
</Note>

<h2 id="claude">
  Connect Claude
</h2>

1. Open **Claude** (web, Desktop, or Code).
2. Add a custom connector or remote MCP server.
3. When Claude asks for connection details, use the values in [Connection details](#connection-details) below.
4. Save the connector. Claude opens ClearPolicy so you can sign in and approve access.
5. Return to **Settings → AI assistants** in ClearPolicy to confirm you are connected.

<Note>
  If you use **Claude Desktop**, add the same server to your `claude_desktop_config.json`, then restart Claude Desktop before connecting.
</Note>

## Example prompts

Try prompts like these after ClearPolicy is connected:

```text theme={null}
Create a draft remote-work policy covering equipment, availability, and data security.
```

```text theme={null}
Update the draft volunteer handbook to add a section on background checks, then show me the revised text.
```

```text theme={null}
Publish the latest draft of the code of conduct after I review it.
```

```text theme={null}
Send our employee handbook to Sarah Jones for signature.
```

```text theme={null}
Who still has a pending acknowledgment request for the code of conduct?
```

```text theme={null}
Send reminders to everyone with an outstanding request for the volunteer policy.
```

```text theme={null}
Has John Davis signed the data privacy policy?
```

<h2 id="connection-details">
  Connection details
</h2>

Use these values when your AI assistant asks for a remote MCP server:

| Setting        | Value                             |
| -------------- | --------------------------------- |
| Server URL     | `https://api.clearpolicy.app/mcp` |
| Transport      | `Streamable HTTP`                 |
| Authentication | `OAuth 2.0`                       |

After you save the server, your assistant should redirect you to ClearPolicy to authorize the connection. You do not need to create API keys or copy bearer tokens.

### JSON configuration

Many MCP clients use this standard remote server shape:

```json theme={null}
{
  "mcpServers": {
    "clearpolicy": {
      "type": "http",
      "url": "https://api.clearpolicy.app/mcp"
    }
  }
}
```

If your client uses a JSON-based MCP config, you can usually adapt this example directly.

## Other supported AI tools

ClearPolicy uses the same connection details for other MCP-compatible clients:

| Provider       | How to connect                                                                                         |
| -------------- | ------------------------------------------------------------------------------------------------------ |
| **Cursor**     | Add a remote MCP server in **Settings** or in `.cursor/mcp.json`.                                      |
| **VS Code**    | Add a remote MCP server with **MCP: Add Server** or in `.vscode/mcp.json` (GitHub Copilot agent mode). |
| **Perplexity** | Add a custom remote connector in **Account Settings → Connectors** (Pro, Max, or Enterprise).          |
| **Grok**       | Add a custom connector from **grok.com → Connectors**.                                                 |
| **Gemini**     | Add a custom MCP connector where your Google AI client supports remote HTTP MCP with OAuth.            |
| **Windsurf**   | Add a remote MCP server in Cascade MCP settings or in `mcp_config.json`.                               |

Other clients that support **remote HTTP MCP servers** and **OAuth 2.0** may also work. If OAuth fails with an invalid redirect error, the client may not be whitelisted yet. Email [support@clearpolicy.app](mailto:support@clearpolicy.app) to request whitelisting of other providers.

<Note>
  Client support for remote MCP and OAuth setup still varies. If your client does not yet support remote HTTP MCP servers with OAuth, ClearPolicy will not appear as a working option until that support is available.
</Note>

## Available actions

The ClearPolicy connection exposes these actions to your AI assistant.

### Documents

<CardGroup cols={2}>
  <Card title="List documents" icon="list">
    Browse documents in your organization. Filter by name to find the right document.
  </Card>

  <Card title="Get document" icon="file">
    View document details, including the current version, draft status, and completion counts.
  </Card>

  <Card title="Create document" icon="file-plus">
    Create a new document as a draft. You can describe what the policy should say in the conversation. The document is not published until you publish the draft.
  </Card>

  <Card title="Get document revision" icon="file-lines">
    Read a draft or published revision, including the body text, so you can review or prepare an update.
  </Card>

  <Card title="Update document revision" icon="pen-to-square">
    Update a draft revision’s body or summary. Published revisions cannot be edited — create a new draft first.
  </Card>

  <Card title="Create document revision" icon="copy">
    Start a new draft revision of an existing document (for example, after the current version is published).
  </Card>

  <Card title="Publish document revision" icon="upload">
    Publish a draft so it becomes the current version for signing. Your assistant should confirm with you before publishing.
  </Card>
</CardGroup>

### People

<CardGroup cols={2}>
  <Card title="List people" icon="users">
    Browse people in your organization. Filter by name or email address.
  </Card>

  <Card title="Get person" icon="user">
    View a person's profile and document compliance summary.
  </Card>

  <Card title="Create person" icon="user-plus">
    Add a new person so they can receive signature requests.
  </Card>
</CardGroup>

### Groups

<CardGroup cols={2}>
  <Card title="List groups" icon="layer-group">
    Browse groups in your organization.
  </Card>

  <Card title="Get group" icon="users-rectangle">
    View group details and related membership information.
  </Card>

  <Card title="Add person to group" icon="user-plus">
    Add a person to a group so they can receive group-based document requests.
  </Card>
</CardGroup>

### Signing requests

<CardGroup cols={2}>
  <Card title="Send signing request" icon="file-signature">
    Send a signature request to one or more people.
  </Card>

  <Card title="List signing requests" icon="list-checks">
    Review requests by document, person, or status.
  </Card>

  <Card title="Get signing request" icon="circle-check">
    Check the status of a specific request.
  </Card>

  <Card title="Send reminder" icon="bell">
    Send a reminder email for a pending request. Reminders are not sent when the latest email delivery failed.
  </Card>

  <Card title="Cancel signing request" icon="ban">
    Cancel a pending request.
  </Card>
</CardGroup>

### Documentation

Your ClearPolicy MCP connection can also answer product how-to questions using the same public documentation as [docs.clearpolicy.app](https://docs.clearpolicy.app) — no second connector required.

<CardGroup cols={2}>
  <Card title="Search docs" icon="magnifying-glass">
    Search product guides and API reference for questions like how reminders work or how to connect Planning Center.
  </Card>

  <Card title="Query docs" icon="book-open">
    Read specific documentation pages when you need exact steps or wording from a guide.
  </Card>
</CardGroup>

These documentation tools do not access your organization data. For live people, documents, and signing status, use the tools above.

## Subscription requirements

Reading data works for supported organizations, but write actions such as creating people, creating or updating documents, publishing drafts, and sending requests require an active subscription or trial. If your organization does not have access, the server returns a message that points you to billing.

## Rate limiting

Each OAuth connection is limited to **120 requests per minute**. AI assistants that make many tool calls in one conversation share this allowance for that connection.

If you exceed the limit, the server returns `429 Too Many Requests`. Wait for the period shown in `Retry-After` before sending more requests.

## Troubleshooting

### I added the server, but nothing happens

Make sure your AI assistant supports remote MCP servers over HTTP and supports OAuth for those servers.

### OAuth failed

Make sure you sign in with a ClearPolicy account that has access to the right organization. If you belong to multiple organizations, confirm you are authorizing the correct one.

### A write action failed because of billing

Your organization needs an active subscription or trial for write operations. Open your billing settings in ClearPolicy and try again.