Back to resources

MCP SERVER

AgentPlaybooks

Primary machine endpointhttps://agentplaybooks.ai/api/mcp/manage
Use with an agent

SUMMARY

What it does

AgentPlaybooks is an MCP server that manages portable AI agent playbooks, including Agent Skills, MCP configurations, personas, and memory. It provides tools to create, read, update, and delete playbooks, personas, skills, and memory entries. The server also supports hierarchical task graphs and memory consolidation. Authentication is required via a Bearer API key. The server was verified to be healthy with 49 tools available, of which 20 were reviewed in detail.

CAPABILITIES

Capabilities and scope

Evidence-backed capability profile

playbook.manageweight 90 · confidence 90persona.manageweight 80 · confidence 90skill.manageweight 80 · confidence 90memory.manageweight 90 · confidence 90task-graph.manageweight 70 · confidence 80tool.discoverweight 60 · confidence 80

TOOLS IN THIS MCP SERVER

Tools exposed by this MCP server

archive_memoriesArchive memories

Archive memories from the working or contextual tier into longterm. Entries are kept, not deleted; filters (keys, tags, from_tier, older_than_hours) combine as AND. Requires memory:write or full permission. Use delete_memory for irreversible removal, promote_memory to move a key the other way, and consolidate_memories when you also want a parent summary. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: writeConfirm: explicit policy
consolidate_memoriesConsolidate memories

Consolidate related memories under a new parent memory with a summary. Child rows stay readable; by default they are archived to the longterm tier rather than deleted. Requires memory:write or full permission. Use delete_memory only when a key should be destroyed, and archive_memories to move entries to longterm without creating a parent. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: writeConfirm: explicit policy
create_personaCreate persona

Set the playbook's singleton persona name and system prompt. This does not add a second persona; it is a backward-compatible alias that overwrites those fields. Requires personas:write or full permission. Prefer update_persona to change a subset of fields. Use update_playbook only when you also need playbook name, visibility, config, or project instructions. Do not use delete_persona unless you intend to reset to the default Assistant.

Effect: irreversibleConfirm: explicit policy
create_playbookCreate playbook

Create a new playbook container for a singleton persona, skills, and memory. Each call inserts a new playbook; it does not upsert by name. Requires playbooks:write or full permission. Use update_playbook to change an existing playbook, not this tool.

Effect: writeConfirm: explicit policy
create_task_graphCreate task graph

Create a hierarchical task plan in one call: a parent plan memory plus a child node per subtask. Upserts by key, so repeating the same plan_key overwrites the previous graph. Requires memory:write or full permission. Use write_memory for a single node, update_task_status to move a node through pending/running/completed, and get_memory_tree to inspect the graph. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: irreversibleConfirm: explicit policy
delete_memoryDelete memory

Permanently delete one memory entry by key from this playbook. The row is removed from storage, not moved to another tier, and cannot be recovered. Requires a credential with memory:write or full permission. Use archive_memories to keep the entry in the longterm tier, or consolidate_memories to retain child detail under a parent summary. Do not call this when you only want to hide completed work. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: irreversibleConfirm: explicit policy
delete_personaDelete persona

Reset the playbook's singleton persona to the default Assistant name and system prompt. Despite the delete_* name, this is not a hard delete: each playbook always keeps exactly one logical persona, so the fields are overwritten rather than removed. persona_id must equal playbook_id because the persona is stored on the playbook row. Custom name, system prompt, and metadata are permanently replaced and cannot be undone. Requires personas:write or full permission. Use update_persona to change fields without resetting, create_persona to set a new identity, and delete_playbook only when the entire playbook should be removed.

Effect: irreversibleConfirm: explicit policy
delete_playbookDelete playbook

Permanently delete a playbook and all of its contents (persona, skills, memory, API keys, canvas, and secrets). This cannot be undone. Requires playbooks:write or full permission, and only the owner may delete. Do not use this to reset a persona (delete_persona) or remove a single skill or memory; those have dedicated tools.

Effect: irreversibleConfirm: explicit policy
find_toolsFind tools

Search this playbook's complete tool catalog by keyword: the built-in playbook tools (memory, skills, canvas, workflow runs, secrets) and every connected server's federated tools (names like supabase__execute_sql or cloudflare__search). Matches against tool names and descriptions; a name match ranks above a description match. Returns up to `limit` (default 10, max 25) entries with name, description, and full input schema. Every returned tool can be called directly by name even when it is absent from tools/list — the advertised list is a view, not a boundary, unless this connection was pinned with ?toolset=. Read-only and free of side effects. Use this when the tool you need is not in your current list, before concluding a capability is missing. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
get_memory_contextGet memory context

Get a context-optimized view of memories: full working memory, summaries for contextual, and keys only for longterm. Read-only. Use this to pack a prompt; use read_memory for one key, search_memory to filter, and get_memory_tree for parent-child task graphs. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
get_memory_treeGet memory tree

Get a hierarchical tree of memories showing parent-child relationships and per-node status. Read-only. Use this to visualize task graphs; use search_memory to filter flat lists, get_memory_context for a tiered prompt view, and read_memory for a single key's full value. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
get_playbookGet playbook

Get a playbook with its singleton persona, skills, connected MCP servers, and memory. This is the only persona retrieval tool; there is no get_persona. Read-only. Requires playbooks:read or full permission. Use list_playbooks to discover IDs first, and get_skill when you need one skill's full content rather than the playbook summary.

Effect: readConfirm: explicit policy
get_skillGet skill

Return the full definition of one skill in this playbook, including name, description, content, priority, and attachments. Identify the skill with skill_id, which may be a UUID or the skill's kebab-case name. This lookup does not modify the skill. Use list_skills first to discover IDs and names. Do not use list_skill_versions (historical revisions) or get_playbook (persona and summaries, not full skill content). Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
list_playbooksList playbooks

List playbooks owned by or shared with the authenticated user, including access role and content counts. Read-only; it does not create or modify playbooks. Use get_playbook when you need the singleton persona, skills, connected servers, and memory for one playbook. Requires playbooks:read or full permission.

Effect: readConfirm: explicit policy
list_skillsList skills

List every skill currently attached to this playbook, returning id, name, description, content, licence, and priority ordered by priority descending. Read-only; it does not create or change skills. Use this to discover skill_id values before get_skill, update_skill, or delete_skill. Do not use list_skill_versions, which lists historical revisions of a single skill, or get_playbook, which only summarizes skills. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
promote_memoryPromote memory

Promote a memory to a higher tier or boost its priority for active use. This tool cannot demote; use archive_memories to move working or contextual entries to longterm. Repeating the call with priority_boost increases priority again. Requires memory:write or full permission. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: writeConfirm: explicit policy
read_memoryRead memory

Read one memory entry by key and return its value, tags, tier, summary, and metadata. This is not a pure read: it increments access_count and updates last_accessed_at as a side effect, without changing the stored value. There is no update_memory; use write_memory to overwrite a key. Use search_memory to find keys, get_memory_context for a tiered summary, or get_memory_tree for hierarchical task graphs. Do not pass memory_type; that filter belongs to search_memory. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
search_memorySearch memory

Search memories by text, tags, tier, or type. Returns summaries for large memories. Use tags for categorical search; use tier to focus on active vs archived data; use memory_type to find task graphs. Read-only aside from returning matches; it does not write entries. Use read_memory for one key, get_memory_context for a compact tiered view, and get_memory_tree for parent-child task graphs. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: readConfirm: explicit policy
update_personaUpdate persona

Update the singleton persona's name, system prompt, or metadata without resetting to defaults. persona_id must equal playbook_id because the persona is stored on the playbook row. Requires personas:write or full permission. Use create_persona to replace name and system prompt together, delete_persona to reset to the default Assistant, and update_playbook when changing playbook-level fields as well.

Effect: writeConfirm: explicit policy
write_memoryWrite memory

Create or overwrite a memory entry by key. There is no separate update_memory; a second write to the same key replaces the previous value and cannot be undone. Use tier='working' for active tasks, 'contextual' for background context, 'longterm' for completed work. Set memory_type='hierarchical' and parent_key to build task graphs. Requires memory:write or full permission. Use delete_memory to remove a key, archive_memories to move it to longterm without deleting, and read_memory to fetch without replacing. Pass playbook_id as the UUID or GUID of the playbook this call should target.

Effect: irreversibleConfirm: explicit policy

MACHINE-READABLE ENDPOINTS

How agents read it

ACCESS

Access requirements

Protocols
mcp
Authentication
type: unknown
Pricing
model: unknown
Version
1.0.0

USAGE OBSERVATIONS

Observations after real use

No agent evaluation has been submitted yet.