AgentPlaybooks MCP server

AgentPlaybooks

One playbook, every agent. A portable operating environment for AI agents — persona, skills, MCP servers, project instructions, and memory in one source of truth.

Keep your agents yours. AgentPlaybooks stores skills, personas, MCP servers, project instructions, and memory in one portable playbook, so you can switch platforms, use several at once, or self-host without vendor lock-in.

Your agent setup stays in sync across Claude, ChatGPT, Cursor, Codex, Gemini, local models, and future platforms. The playbook is the portable source of truth—not any single vendor or editor.

It is not another skill store or MCP registry. Skills and MCP connections are parts of a playbook; the playbook is the whole job. That holds for agents with a body too: a skill can carry demonstrations, recordings of the task in the order a robot performs them.

Highlights

What a playbook holds

teams can execute the same playbook without sharing work products

• Persona: 1 per playbook, stored directly on the playbook record
• Instructions: always-on project rules — the AGENTS.md / CLAUDE.md content
• Skills: SKILL.md documents in the Agent Skills format, frontmatter preserved across every client
• Skill attachments: bundled scripts, references, and templates, round-tripped by the CLI
• Demonstrations: recordings of a skill being performed — YouTube, a pinned URL, or a LeRobot dataset — with timestamped segments, for agents that learn by watching
• MCP servers: tools and resources in Model Context Protocol format
• Memory: key-value store with tags and descriptions, with a native Hermes memory provider
• Hermes Tools plugin: connect playbook skills, MCP/OpenAPI tools, and credentials
• Canvas: versioned markdown work documents, scoped to a playbook run, so several

Credentials, without handing them over

name and the platform injects it server-side (use_secret), so the value never enters an agent's context. Optional per-secret host allow-lists, and an expiry that is enforced: an expired secret is refused by every path that would use it.

• Secrets vault: AES-256-GCM, per-user derived keys. Agents reference a secret by

playbook, with their credentials resolved from that same vault by name

• Federation: other MCP servers and OpenAPI services become tools on your

chain, and explicitly confirm retention purges with apb audit.

• Audit trail: every federated call and every vault operation, refusals included
• Audit evidence from the CLI: export JSONL/CSV, verify the per-playbook hash

Getting it into your tools

Shortened. The full README is on GitHub.