Use AI tools with ClearPolicy via MCP

Connect ClearPolicy to Claude, ChatGPT, and other MCP-compatible AI clients so you can manage documents, people, and signing requests with natural language.

Model Context Protocol (MCP) lets AI clients connect to external tools over a standard interface. ClearPolicy exposes a remote MCP server so you can use natural language to manage documents, people, and signing requests from Claude, ChatGPT, and other MCP-compatible clients.

When you connect ClearPolicy, your AI client is redirected to ClearPolicy for OAuth. You sign in, approve access, and return to the client. You do not need to create API keys or copy bearer tokens.

The ClearPolicy listings for OpenAI and Claude are still pending approval. Until those listings are live, add ClearPolicy manually with the connection details on this page.

What you can do

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

• Send a document for signature or acknowledgment
• 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
• Review compliance across documents in your organization

Connection details

Use these values when your AI client 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 client should redirect you to ClearPolicy to authorize the connection.

Manual setup

Many MCP clients use this standard remote server shape:

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

Claude Desktop

Add the same server definition to your claude_desktop_config.json.

Restart Claude Desktop after you save the file. The first time you use ClearPolicy, Claude opens the ClearPolicy OAuth flow so you can sign in and authorize access.

ChatGPT and other MCP clients

If your client supports remote MCP servers, add a new server with the same URL, transport, and OAuth settings shown above. The exact UI and JSON format vary by client, but the ClearPolicy connection details stay the same.

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.

Available tools

The ClearPolicy MCP server exposes these tools to connected AI clients.

Documents

Browse published documents in your organization. Filter by name to find the right document. View document details, including the current version and completion counts. Create a new signable document in ClearPolicy from a public PDF or Word document URL.

People

Browse contacts in your organization. Filter by name or email address. View a contact's profile and document compliance summary. Add a new contact so they can receive signing or acknowledgment requests.

Signing requests

Send a signature or acknowledgment request to one or more people. Review requests by document, person, or status. Check the status of a specific request. Send a reminder email for a pending request. Cancel a pending request.

Example prompts

You can use prompts like these after ClearPolicy is connected:

Send our employee handbook to Sarah Jones for signature.

Who still has a pending acknowledgment request for the code of conduct?

Send reminders to everyone with an outstanding request for the volunteer policy.

Has John Davis signed the data privacy policy?

Subscription requirements

Reading data works for supported organizations, but write actions such as creating people, importing documents, 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.

Troubleshooting

I added the server, but nothing happens

Make sure your AI client 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.