Skip to main content

ClarityLoop MCP

ClarityLoop MCP is the right integration when you want AI tools to work with your ClarityLoop context directly instead of relying on pasted snippets or manual summaries. It is personal access, not a workspace-wide shared credential.

What ClarityLoop MCP helps with​

Use ClarityLoop MCP when you want an MCP-compatible client to:

  • pull ClarityLoop context into an AI workflow
  • help you draft or refine feedback
  • inspect goals, 1:1s, and related workspace context
  • work with live ClarityLoop data from a tool like ChatGPT, Claude Desktop, or an IDE assistant

Watch the walkthrough​

Watch this walkthrough to see how MCP works, which endpoints to use, and how to connect supported clients cleanly.

Who sets it up​

Each person generates and manages their own MCP API keys. These keys are personal to the account that created them.

Generate an MCP API key​

  1. In ClarityLoop, open Workspace > Integrations.
  2. Scroll to Personal Integrations.
  3. Open Personal MCP API Keys.
  4. Generate a new API key.
  5. Copy it immediately and store it safely.

The full key is shown only once. Keys start with clp_mcp_.

Two ways to connect​

OAuth-style client flow​

Use this when the client supports the standard MCP connection flow.

MCP URLs:

  • HTTP endpoint: https://mcp.clarityloop.com/mcp
  • SSE endpoint: https://mcp.clarityloop.com/sse

This is the cleaner option for supported clients such as ChatGPT, Claude Desktop, or MCP Inspector.

API key header flow​

Use this when your tool expects a direct header-based connection.

Header:

X-ClarityLoop-Api-Key: <your_mcp_api_key>

Endpoint:

https://mcp.clarityloop.com/mcp

Client examples​

MCP Inspector​

npx @modelcontextprotocol/inspector https://mcp.clarityloop.com/mcp

Claude Desktop​

{
  "mcpServers": {
    "ClarityLoop": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.clarityloop.com/sse"
      ]
    }
  }
}

Security and key rotation​

  • treat MCP API keys like personal secrets
  • revoke keys you no longer use
  • if a key is exposed or lost, generate a new one and update the client

Because access is personal, revoking one key does not affect other people in the workspace.

FAQs​

Is an MCP key shared across the workspace?

No. MCP API keys are personal to the account that created them.

What if I lose the key?

Generate a new one and update the client. The original full key cannot be recovered.

Which endpoint should I use?

Use /mcp for direct MCP clients and /sse when the client or wrapper expects an SSE-style remote connection.

Can I revoke a key later?

Yes. You can revoke keys from the same Personal MCP API Keys area where you created them.