Loop Tasker MCP Server

The Loop Tasker MCP bridge connects local MCP clients to the existing hosted mcpEndpoint. It supports workspace keys for shared automation and personal keys that can switch between the workspaces allowed when the key is created. Loop Tasker stores only the SHA-256 hash of every API key.

Quick start

Create a v2 key under Settings → Integrations → MCP or Workspace Settings → Integrations → MCP, then use the generated client configuration. The generic JSON form is:

{
  "mcpServers": {
    "looptasker": {
      "command": "npx",
      "args": ["-y", "@looptasker/mcp-server@latest"],
      "env": {
        "LOOPTASKER_API_KEY": "ltmcp_your_key",
        "LOOPTASKER_BACKEND_URL": "https://europe-north1-looptasker-swetr.cloudfunctions.net/mcpEndpoint"
      }
    }
  }
}

Codex uses the equivalent [mcp_servers.looptasker] TOML table in ~/.codex/config.toml. Claude Code/project setups use .mcp.json, and Google Antigravity uses ~/.gemini/config/mcp_config.json. Loop Tasker’s MCP settings screen generates each format.

Capabilities

• Efficient cross-entity search and exact #taskCounterId references
• Tasks, comments, subtasks, watchers, recurrence and reversible lifecycle
• Notes with safe replace/append/prepend updates, pinning, trash and restore
• Spaces, project updates, tags and manager-controlled groups
• Personal reminders, timers and time reports
• Attachment metadata, direct local upload, secure download, rename and notes

Permanent deletion and attachment deletion are intentionally unavailable. Existing v1 keys keep their legacy mutation scope; recreate a key to opt into v2 mutations and the optional files permission.

Local attachment safety

Attachment tools may only read or write paths beneath LOOPTASKER_ALLOWED_FILE_ROOTS. Separate multiple roots with the platform path delimiter (; on Windows, : on macOS/Linux). If unset, the bridge permits only its current working directory. Downloads without an explicit output path go to the operating-system temporary directory. Path traversal, symlink escape and accidental overwrite are rejected.

Build and test

cd mcp-server
pnpm install
pnpm test

Node.js 20 or newer is required. The hosted endpoint remains compatible with the published 2.0.1 bridge while 2.1.0 is rolled out.