Ask Claude Code about your own week.
TeamLaboration runs a Model Context Protocol server alongside the dashboard on the same local port. Once you register it, Claude Code (or any MCP client) can query your sessions, summaries, and weekly reports as first-class tools.
Register the server
With the daemon running, register the MCP endpoint with Claude Code:
claude mcp add --transport http teamlaboration http://localhost:7842/mcp/ Keep the trailing slash on /mcp/. Without it Starlette responds with a 307 redirect that the MCP HTTP client does not follow, and the handshake silently fails. Both localhost and 127.0.0.1 work — the daemon binds IPv4 and IPv6 loopback.
Verify the connection — you should see teamlaboration ✓ connected:
claude mcp list To remove or re-register:
claude mcp remove teamlaboration What you can ask
Once connected, talk to Claude Code in plain English — it picks the right tools on its own:
- · "Summarize my week."
- · "What did I work on in the auth project last week?"
- · "Flag the session about the migration as a highlight."
- · "Find all sessions where I dealt with rate limiting."
- · "Regenerate the summary for the session from Tuesday morning."
The 13 tools
Configuration mutations — API key, polling cadence, notifier credentials — are intentionally not exposed as MCP tools. They're a settings concern, not an automation one.
List all stored weekly reports.
Fetch a single weekly report by week ID.
List historical versions of a weekly report after regeneration.
Trigger generation of the rollup for a given week (uses the daemon's Anthropic key).
Export a weekly report as Markdown or JSON.
Used by the slash-command workflow — Claude posts a weekly narrative it wrote itself.
All per-chat summaries that fall inside a given weekly window.
List sessions across all projects, with status (pending/summarized/failed).
Get a single session row with its summary if present.
Full-text search across stored summaries.
Flag a session as a highlight, archive, etc.
Re-summarize a single session — useful after prompt changes.
Sessions queued for summarization.
Get the raw conversation turns (used by the slash-command workflow).
Used by the slash-command workflow — Claude posts a chat summary it wrote itself.
Daemon health, last poll, next poll, counts of sessions by status.
Force an immediate poll of ~/.claude/projects/ without waiting for the interval.
List all discovered Claude Code projects.
Slash-command workflow (no API key in TeamLaboration)
If you'd rather not give the daemon an Anthropic key, set ai_enabled = false in Settings. The daemon will keep collecting and tracking sessions but will never call the Anthropic API on its own.
From inside any Claude Code session, the MCP server exposes two prompts that flip the model around — Claude itself reads pending sessions and writes summaries back:
/mcp__teamlaboration__summarize_pending /mcp__teamlaboration__weekly_report The first prompt makes Claude pull pending sessions via list_pending_sessions + get_session_raw, write per-chat summaries, and post them back through submit_summary. The second does the same dance for a weekly narrative via submit_weekly_report.
This is useful when you want to summarize using whatever model your Claude Code session is already running, or when corporate policy keeps API keys out of background services.
Other MCP clients
The server speaks plain MCP-over-HTTP, so anything that implements the protocol works — Claude Desktop, Cursor, custom agents. Point them at http://localhost:7842/mcp/ (with the trailing slash) and use whatever registration mechanism your client provides.