Stop Copy-Pasting Task Context to AI

Add this entry to your client's MCP config (for Claude Code: `.mcp.json` in your project root; for Claude Desktop: Settings → Developer → Edit Config). The endpoint, transport, and auth header are exactly what every MCP-native client expects.

{
  "mcpServers": {
    "mcptask-online": {
      "type": "sse",
      "url": "https://mcptask.online/mcp/sse",
      "headers": { "Authorization": "Bearer ${MCPTASK_TOKEN}" }
    }
  }
}

1. 1
   Sign up at mcptask.online (free, 30-day Professional trial)
2. 2
   Open Settings → API Access → click "Generate token"
3. 3
   Copy the token, then `export MCPTASK_TOKEN=mcptask_...` in your shell (or add it to ~/.zshrc / ~/.bashrc)
4. 4
   Paste the config above into `.mcp.json` (or your client's MCP settings)
5. 5
   Restart your AI client
6. 6
   Ask the agent: "List the next open task from my mcptask.online project."

Where this goes: `.mcp.json` (Claude Code) or the developer's MCP config dialog (Claude Desktop, Cursor, Cline). The `${MCPTASK_TOKEN}` reference is resolved from the environment variable — export it once in your shell profile so every client picks it up.

In plain English, ask the agent to work on something. The agent resolves `mcptask://pieces/{account_code}/{piece_id}` against mcptask.online over MCP — no copy-paste.

"Read task #47 and implement the login feature"

The URI pattern is the canonical read entry point. Everything in mcptask.online is a **piece** — tasks, stories, epics, recurents, projects — and they all share the same `mcptask://pieces/{account_code}/{id}` shape.

AI receives:

• check_circlePiece name and full description
• check_circleParent epic/story context
• check_circleAcceptance criteria
• check_circleRelated pieces and dependencies
• check_circleAll comments and discussion
• check_circleAttached files (specs, designs)
• check_circleWork history

When done, the agent calls MCP to log progress — duration, what changed, status, blockers. You can ask it to log, or you can run the optional `mcptask_runner` gem that handles the autonomous loop end-to-end.

• check_circleLog time spent
• check_circleDescribe what was done
• check_circleUpdate task status
• check_circleAdd notes and blockers