ClearPolicy

app.clearpolicyPublished by clearpolicy.appOfficial publisherv1.0.1Updated Oct 24, 2026

Authenticated MCP server for ClearPolicy policy and compliance workflows.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Connects an assistant to ClearPolicy for authenticated policy and compliance workflows.

What you can do
ClearPolicy is a remote MCP server reached over streamable HTTP at its own API endpoint. It is described as an authenticated server for policy and compliance workflows, so an assistant can work with ClearPolicy policy and compliance tasks through the connection. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Consider it when your organization already uses ClearPolicy and you want an assistant to take part in policy and compliance work without leaving the conversation. It is not useful without a ClearPolicy account.
Requirements
A remote MCP client that supports streamable HTTP, plus OAuth sign-in to ClearPolicy. No packages, environment variables or headers are declared. Network access to the ClearPolicy API endpoint is required.
Before you install
Access is granted through OAuth, so the assistant acts with the permissions of the account that authorizes it; review what that account can see and change before connecting. The manifest lists no tools, so confirm in ClearPolicy what actions the connection allows. Policy and compliance data may be sensitive.

Installation

In SourceWeft

  1. Open ClearPolicy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.clearpolicy%2Fclearpolicy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clearpolicy": {
      "type": "http",
      "url": "https://api.clearpolicy.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.