Skip to main content

ClarityLoop MCP

ClarityLoop MCP lets you connect MCP-compatible clients (ChatGPT, Claude Desktop, IDE assistants, or custom tools) to your ClarityLoop data. Use it to pull context, summarize updates, draft feedback, or explore goals directly inside your AI workspace.

Watch the walkthrough​

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

What the MCP integration includes​

  1. Access ClarityLoop context in MCP clients

    • Pull feedback, 1:1s, OKRs, and other workspace data into your AI tool.
    • Keep context fresh without switching back and forth between apps.

  2. Two authentication options

    • OAuth for clients that support it (recommended).
    • API key headers for lightweight or custom integrations.

  3. Personal, revocable access

    • MCP API keys are personal to your account.
    • You can rotate or revoke them anytime.

Generate an MCP API key​

  1. In ClarityLoop, go to Workspace → Integrations.
  2. Scroll to Personal Integrations → Personal MCP API Keys.
  3. Click Generate API Key.
  4. Copy the key and store it securely (it’s shown only once).

✅ MCP keys start with the prefix clp_mcp_.

Use OAuth when your client supports it (ChatGPT, Claude Desktop, MCP Inspector).

  1. Start the connection using your MCP server URL.
  2. Your client will open a browser window for authorization.
  3. When prompted, paste your MCP API key to authorize access.

MCP URLs

  • HTTP endpoint: https://mcp.clarityloop.com/mcp
  • SSE endpoint (for mcp-remote): https://mcp.clarityloop.com/sse

Example: MCP Inspector​

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

Example: Claude Desktop​

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

Connect using API key headers​

Use this for tools that only support custom headers or direct HTTP calls.

Header

X-ClarityLoop-Api-Key: <your_mcp_api_key>

Example (HTTP endpoint)

https://mcp.clarityloop.com/mcp

Security and key rotation​

  • Keep MCP API keys private.
  • Revoke any key you no longer use.
  • If a key is lost, generate a new one and update your MCP client.

FAQs​

Is the MCP key shared across my workspace?

No. MCP API keys are personal to your account.

What if I lose my key?

Generate a new key and update the MCP client. Lost keys cannot be recovered.

Which endpoint should I use?

Use /mcp for direct MCP clients and /sse when a tool uses mcp-remote.