MCP Task Manager for Claude Code and Streamable HTTP Clients

What Is the CalmLoop MCP Task Manager?

The Model Context Protocol (MCP) lets compatible AI hosts use external tools and data. CalmLoop exposes a stateless Streamable HTTP endpoint for your Pending Tasks, daily Focus Zone, notes, history, and projects.

Regular web registration and login stay unchanged. You create and revoke separate MCP personal access tokens in the signed-in web app, and each token controls what one trusted MCP host can do.

Create a Personal Access Token

1. Register or sign in to the normal CalmLoop web app.
2. Open Settings > MCP Access.
3. Create a named token with Read Only, Read & Update, or Full Access for 30, 90, or 365 days.
4. Copy the token once. CalmLoop never displays the raw secret again.
5. Configure it as Authorization: Bearer <token> in a trusted host, using HTTPS only.
6. Revoke the token from Settings > MCP Access when the host is retired or the secret may be compromised.

Claude Code Setup

Replace the placeholder with the token you just copied, then run this command in a terminal on the trusted device:

claude mcp add --transport http --header "Authorization: Bearer YOUR_CALMLOOP_MCP_TOKEN" calmloop https://calmloop.in/mcp

Run the substituted command in a private terminal session whose history will not record the secret. Claude Code uses local scope by default; keep the token out of project scope and source-controlled .mcp.json files. Run claude mcp list to confirm the server and use /mcp inside Claude Code to inspect connection status.

Read the official Claude Code MCP documentation.

Codex Setup

Set CALMLOOP_MCP_TOKEN through your operating system or a secret manager in the environment that will launch Codex. Keep the real token out of this registration command, Codex configuration, project files, and shell history.

codex mcp add calmloop --url https://calmloop.in/mcp --bearer-token-env-var CALMLOOP_MCP_TOKEN

Run codex mcp list to confirm the server and use /mcp inside Codex to inspect connection status. If the environment variable is temporary, start Codex from the same terminal session so it can read the token.

Read the official Codex MCP documentation.

OpenCode Setup

These instructions target the current stable opencode client. The separate OpenCode 2.0 beta uses the opencode2 binary and a different, changing configuration schema, so this block does not cover it.

Set CALMLOOP_MCP_TOKEN in the environment that will launch OpenCode, then add the server to the global ~/.config/opencode/opencode.json configuration:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "calmloop": {
      "type": "remote",
      "url": "https://calmloop.in/mcp",
      "enabled": true,
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:CALMLOOP_MCP_TOKEN}"
      }
    }
  }
}

This file stores only the environment-variable reference; never replace it with the real token. Launch OpenCode from an environment where the variable is available, then run opencode mcp list to confirm connection status.

Read the official stable OpenCode MCP documentation.

Other Streamable HTTP Clients

A compatible client must support a secret custom Authorization header. Configure the endpoint and header as separate secret-aware fields:

Endpoint: https://calmloop.in/mcp
Authorization: Bearer YOUR_CALMLOOP_MCP_TOKEN

Use only the placeholder in templates and documentation. Never place a real token in a URL, page markup, prompt, or source-controlled file. Client labels vary; select Streamable HTTP or remote HTTP rather than deprecated SSE.

Claude and Claude Desktop Connector Compatibility

The current Claude and Claude Desktop account-brokered custom connector UI expects an OAuth connection and does not offer a field for this static custom Authorization header. CalmLoop intentionally has no OAuth flow, so that connector path is not supported by this PAT setup.

Use Claude Code or another MCP host that explicitly supports storing and sending a secret header. This guide does not claim universal MCP host compatibility.

Read Anthropic's official remote custom-connector guide.

Access Profiles

Choose the least-privileged profile that the host needs. Access profiles do not bypass CalmLoop's existing ownership, subscription, validation, Focus Zone, or recurrence rules. For example, create operations that require an active trial or subscription remain gated.

14 Available MCP Tools

The Full Access profile exposes exactly these tools; lower profiles expose only their permitted subset:

3 Read-Only MCP Resources

Example MCP Task Workflow

Personal Access Token Safety

Create one token per trusted host or device, choose least privilege, and set an explicit 30-, 90-, or 365-day expiry. CalmLoop shows the secret once; revoking one token is immediate and does not disrupt your other tokens.

Use HTTPS only and review how the MCP host stores custom headers before configuring it. Enter the PAT into the host's secret configuration yourself. Never ask a model to read or store the PAT, and never paste it into a conversation, log, screenshot, repository, or support message. If exposure is possible, revoke it in Settings immediately and create a replacement.