Repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP.
MCPpedia last refreshed this data
io.github.ihorponom/agentpack is an MCP server that repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP. Its tool list has not been published yet over sse and http, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-ihorponom-agentpack": {
"args": [
"-y",
"agentpack-cli"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'agentpack-cli' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked agentpack-cli against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in finance
OKX trading MCP server — connect AI agents to spot, swap, futures, options & grid bots via the Model Context Protocol.
Ledger of AI-agent money on Base: payments, detections, Gate, signed Pass, Agent Books, free checks
Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 102 tools, USDC, 20 chains.
MCP Security Weekly
Get CVE alerts and security updates for io.github.ihorponom/agentpack and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Repo-native task continuity for AI coding agents.
Agent memory remembers how you work. Agentpack remembers where the task stands.
Your agent spent an hour on a task. It found the cause, rejected two approaches, and wrote down the next step. Then the context was compacted, or the chat closed. The next session starts from zero and does the same investigation again.
Agentpack keeps the task state in your repo. Connected agents record the goal, decisions, dead ends, verification evidence, and checkpoints in .agentpack/ while they work. Then the next session loads that state and continues: the same agent after compaction, a different client, or you next week.
Here it is in action. In session 1, an agent works on a flaky test and records a decision, a dead end, and a checkpoint through the Agentpack MCP tools. In session 2, the next day with an empty context, one load_context call brings the task back:

▶ Watch the 80-second explainer, with sound
To try the same flow by hand from the CLI, see docs/DEMOS.md.
AGENTS.md, CLAUDE.md, Cursor rules) tell agents when to load and record state.Claude Code memory, Codex memories, and CLAUDE.md or AGENTS.md keep how to work: your preferences, project conventions, and facts that stay true. Agentpack keeps where the work is: the goal of the current task, its constraints, decisions, dead ends, next actions, and verification result.
| Agent memory | Agentpack | |
|---|---|---|
| Holds | Preferences, conventions, long-lived facts | The state of one task |
| Lives in | The profile or account of one client | .agentpack/ in the repo, local by default, portable with task bundles |
| Read by | That client only | Any MCP client: Claude Code, Codex, Cursor, Claude Desktop |
| Shape | Free-form notes, recalled by relevance | A Task Passport per task: goal, lifecycle, the paths it may change, and verification bound to a commit |
| Staleness | Not tied to file changes | Notes about files store the file hash, so Agentpack flags a note when its file changes |
Use both. Memory keeps how you like to work. Agentpack keeps what the task needs next.
Agentpack needs Node.js 20 or later.
npm install -g agentpack-cli
cd path/to/your/repo
agentpack init # once per repo
agentpack install claude --write # per client: codex | claude | cursor | claude-desktop
agentpack install git-hooks --write # optional: task gate check before each commit
Restart or reconnect your coding agent, and approve the Agentpack server or hooks when the client asks. From then on, the agent loads the task state