MCP server (Beta)

The Clearly AI MCP server lets AI assistants — such as Claude Desktop, Cursor, Windsurf, and other MCP-compatible clients — interact with Clearly AI on your behalf. You can create Projects, run Reviews, and retrieve Review results through natural language conversation with your AI assistant.

All actions taken through the MCP server run as you, using your Clearly AI identity and permissions.

What you need

• A Clearly AI account with access to at least one Organization.
• An MCP-compatible AI client (Claude Desktop, Cursor, Windsurf, VS Code with Copilot, or any client that supports the MCP HTTP transport).
• Your tenant URL, typically https://{tenant}.clearly-app.com.

Connect your AI client

Add the Clearly AI MCP server to your client's configuration. The server uses HTTP transport with OAuth 2.0 authentication — your client will open a browser window to authenticate you the first time you connect.

Configuration

Add the following to your MCP client configuration:

{
  "mcpServers": {
    "clearly": {
      "type": "http",
      "url": "https://{tenant}.clearly-app.com/mcp"
    }
  }
}

Replace {tenant} with your Clearly AI tenant name. Your tenant name is the subdomain in your Clearly AI URL.

Client-specific setup

What you can do

Once connected, ask your AI assistant to perform Clearly AI tasks in natural language. The MCP server exposes tools that the assistant calls automatically based on your requests. Your AI client will list the available tools when you connect.

Some tools read data and others change Clearly AI resources. The tools available to a client depend on your Clearly AI permissions.

Security practices

• Connect only MCP clients that your organization trusts. The client stores and protects the OAuth token under its own security model.
• Review the tools listed by the client before using them. Enable the client's confirmation or approval controls for actions that create, update, assign, submit, or delete data.
• Use a Clearly AI account with only the access needed for the work.
• Treat instructions contained in project sources, tickets, linked pages, and generated content as untrusted. Do not approve a tool call solely because that content requests it.
• Review the target organization, project, and proposed changes before approving a state-changing tool call.
• Remove the MCP server and its stored authorization from the client when the connection is no longer needed. Follow the client's documentation for its token-removal process.

Example prompts

Start with read-only requests while you verify the connection and the client's approval behavior:

• "Get all the non-compliant answers for the payments-service review."
• "Summarize the open reviews in the checkout-api project."
• "Show me the projects I can access without changing them."

Authentication

The MCP server uses OAuth 2.0. When your AI client first connects to the server, it opens a browser window where you sign in with your existing Clearly AI credentials. After you authenticate, the client stores the token and reuses it for future requests. Clearly AI does not control how a third-party client stores that token.

If your session expires, your client will prompt you to re-authenticate.

Related

• API reference — REST API for programmatic access
• CLI — Command-line interface for scripting
• Reviews — How reviews work in Clearly AI