ClearPolicy

Connect ChatGPT and Claude

Authorize an AI assistant to work with your ClearPolicy organization, then use it for documents, people, requests, and product help.

Connect ChatGPT or Claude to ask about your organization's documents and take supported actions in conversation. Each team member connects their own AI account through OAuth, signing in to ClearPolicy and approving access.

This connection can act on your organization. The in-app Support assistant is for product help; see get support.

Before you connect

• Sign in to ClearPolicy and select the organization you want the assistant to use.
• Complete any setup requested during authorization. A person and a published document are needed before this connection can be authorized.
• Your team role determines which actions are allowed.
• Write actions require an active trial or subscription.

Connect ChatGPT

1. Open the ClearPolicy listing in the ChatGPT Apps library.
2. Follow the installation prompts and sign in to ClearPolicy.
3. Check the organization shown and approve access.
4. Return to Settings → AI assistants in ClearPolicy to check the connection.

Manual MCP setup

If your ChatGPT plan supports custom MCP connectors, you can add one using the connection details. Follow ChatGPT's current connector instructions; menu names and plan availability vary.

Connect Claude

1. Open Claude's connector settings and add a custom remote connector, where supported by your plan.
2. Enter the ClearPolicy server URL from connection details.
3. Follow the sign-in prompt to ClearPolicy, check the organization, and approve access.
4. Check Settings → AI assistants in ClearPolicy after connecting.

For Claude Code or another MCP client, follow that client's remote HTTP and OAuth setup instructions. Configuration formats differ between clients.

Connection details

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

The client should open ClearPolicy for authorization. You do not need to create or paste a REST API token.

Available actions

Area	Supported work
Documents	List documents, get details, add a rich-text draft, read revisions, update a draft, start a new draft revision, and publish a draft.
People	List people, get a person's details, and add a person.
Groups	List groups, get group details, and add an existing person to a group.
Signing requests	List or inspect requests, send requests, remind people, and cancel pending requests.
Documentation	Search product help and read specific documentation pages.

Document drafting works with editable rich-text content. These tools do not rewrite an uploaded PDF or Word document as rich text. Manage uploaded content in the app.

Published revisions cannot be edited; start a draft revision first. Changes to a document's Requires a signature setting are made in the app, not through these tools.

Review the proposed document and audience before confirming publishing, sending, reminders, or group changes. Adding a person to a group can trigger that group's automatic request emails.

Example prompts

Draft a volunteer code of conduct covering attendance, safety, and confidentiality. Leave it unpublished for review.

Who still needs to sign the employee handbook?

Find Alex Morgan by email alex@example.com and show me their document status.

Show me the outstanding requests for the safety policy before sending reminders.

Documentation and organization data

The Search docs and Query docs actions use public product documentation. They do not look up a person's live status. The people, document, and signing-request actions provide organization data.

The docs connection used by in-app Support is different from the product MCP server above. Connecting ChatGPT or Claude to ClearPolicy already includes the documentation actions; a second connector is not needed.

Other supported AI tools

Other clients need support for remote Streamable HTTP MCP and OAuth. Use the same server URL with the client's own setup instructions. If authorization reports an unsupported or invalid redirect, contact support with the client name and error.

Subscription requirements

Supported read actions and write actions have different access requirements. Adding people, editing or publishing documents, and sending requests require an active trial or subscription. Your team permissions still apply.

Rate limiting

Each OAuth token is limited to 120 requests per minute. If the server returns 429 Too Many Requests, wait for the interval indicated by Retry-After before retrying.

Troubleshooting

The connection sends me to setup

Finish selecting or setting up the organization, add a person and a published document, and continue authorization.

I added the server, but nothing happens

Check that the client supports remote HTTP MCP and OAuth, and that connectors are available on your plan.

OAuth failed or the wrong organization appears

Sign in with the intended team member account and confirm the organization at authorization. Reconnect if the connection was authorized for a different organization.

An action is unavailable or denied

Check your team role and the supported actions above. The integration does not expose every action available in the app.

A write action failed because of billing

Open Settings → Billing in the connected organization and check its trial or subscription. See billing help.