M
matebenyovszky/agentplaybooks
Equip once. Run anywhere. Portable AI agents and toolkits—no vendor lock-in.
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"matebenyovszky-agentplaybooks": {
"url": "https://agentplaybooks.ai/api/mcp/manage"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint declares a required request header Authorization (Bearer AgentPlaybooks user API key (for example: Bearer apb_live_...)). Using it means bringing your own credentials.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"matebenyovszky-agentplaybooks": {
"type": "http",
"url": "https://agentplaybooks.ai/api/mcp/manage"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http matebenyovszky-agentplaybooks https://agentplaybooks.ai/api/mcp/manage
Claude Code does not read a config file; add the server with this command.
Client config (built from the install command this repo gives)
{
"mcpServers": {
"matebenyovszky-agentplaybooks": {
"command": "npx",
"args": ["@agentplaybooks/cli@latest"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"matebenyovszky-agentplaybooks": {
"command": "npx",
"args": ["@agentplaybooks/cli@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio matebenyovszky-agentplaybooks -- npx @agentplaybooks/cli@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 11 ★ · matebenyovszky/agentplaybooks · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 11 ★ · 23 sources · mcp
- Install
npx @agentplaybooks/cli@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @agentplaybooks/cli@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
matebenyovszky/agentplaybooks；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# AgentPlaybooks
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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
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
teams can execute the same playbook without sharing work products
Credentials, without handing them over
Secrets vault: AES-256-GCM, per-user derived keys. Agents reference a secret by
name and the platform injects it server-side (usesecret), 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.
Federation: other MCP servers and OpenAPI services become tools on your
playbook, with their credentials resolved from that same vault by name
Audit trail: every federated call and every vault operation, refusals included
Getting it into your tools
Claude: one plugin brings every playbook in your account into claude.ai,
Claude Desktop, Cowork, Claude Code, and mobile, signing in with OAuth — no
API key. Or add a single playbook as a custom connector. See
AgentPlaybooks in Claude.
Cursor and VS Code: one-click install links for the account or a single
playbook — on each playbook's Integrations tab, and in
MCP Integration.
CLI + portable Agent Plugin: audit your local agent config, then sync one playbook
to Claude Code, Cursor, ChatGPT/Codex, Google Antigravity, Grok Bot and Hermes
Agent Plugins 1.0: install the project plugin or export a single playbook as
plugin.json, mcp.json, and complete Agent Skills directories. Compatible
MCP hosts can also discover hosted playbook skills through the MCP Skills extension.
Private, versioned central backups are separate from installable plugin exports;
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
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
teams can execute the same playbook without sharing work products
Credentials, without handing them over
Secrets vault: AES-256-GCM, per-user derived keys. Agents reference a secret by
name and the platform injects it server-side (usesecret), 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.
Federation: other MCP servers and OpenAPI services become tools on your
playbook, with their credentials resolved from that same vault by name
Audit trail: every federated call and every vault operation, refusals included
Getting it into your tools
Claude: one plugin brings every playbook in your account into claude.ai,
Claude Desktop, Cowork, Claude Code, and mobile, signing in with OAuth — no
API key. Or add a single playbook as a custom connector. See
AgentPlaybooks in Claude.
Cursor and VS Code: one-click install links for the account or a single
playbook — on each playbook's Integrations tab, and in
MCP Integration.
CLI + portable Agent Plugin: audit your local agent config, then sync one playbook
to Claude Code, Cursor, ChatGPT/Codex, Google Antigravity, Grok Bot and Hermes
Agent Plugins 1.0: install the project plugin or export a single playbook as
plugin.json, mcp.json, and complete Agent Skills directories. Compatible
MCP hosts can also discover hosted playbook skills through the MCP Skills extension.
Private, versioned central backups are separate from installable plugin exports;
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/matebenyovszky-agentplaybooks/)
- Source
- awesome · https://github.com/matebenyovszky/agentplaybooks
- Browse by field
- MCP servers
- Traction
- 11 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.