Repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP.
Connect Agentpack to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP. The agentpack mcp server is what makes that connection.
Here it is live. Session 1: Claude Code investigates a flaky test and records what it learns through the Agentpack MCP tools. Session 2, next day, empty context: the agent loads the task state and picks up exactly where the first session stopped — no re-investigation:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Local — first.** Plain files in your repo. No cloud, no telemetry, no network callsAgent — oriented.** A local MCP server plus generated project instructions (AGENTS.md, CLAUDE.md, Cursor rules) tell agents when to load and record stateHuman — friendly.** The same state is available through the CLI for inspection, debugging, and manual handoffBest — effort redaction of secret-looking values in stored context and handoff outputThe server ships on npm as agentpack-cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agentpack's toolset — Local, Agent, Human and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ihorponom; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Local | first.** Plain files in your repo. No cloud, no telemetry, no network calls. |
| Agent | oriented.** A local MCP server plus generated project instructions (AGENTS.md, CLAUDE.md, Cursor rules) tell agents when to load and record state. |
| Human | friendly.** The same state is available through the CLI for inspection, debugging, and manual handoff. |
| Best | effort redaction of secret-looking values in stored context and handoff output. |
{
"mcpServers": {
"agentpack": {
"command": "npx",
"args": ["-y", "agentpack-cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.