Agent Deck
Keep the way you work consistent across coding agents and workspaces. Agent Deck gives every agent the right playbooks, tools, and credentials from one governed source of truth.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @agent-deck/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add agent-deck-cli -- npx -y @agent-deck/cli@2.5.4Execute em um terminal.
{ "mcpServers": { "agent-deck-cli": { "command": "npx", "args": [ "-y", "@agent-deck/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
Abrir
Watch the 100-second overview — one playbook across agents and workspaces.
Bringing a friend (or starting cold)? Follow the one-page friend path: cold machine → first deck switch → first Dealer issue.
You teach one coding agent how you work: how to open a PR, write a ticket, check a release, or use your knowledge base. Then you switch to another agent and teach it all again.
One MCP endpoint, registered once.
The execution half is agent-dealer: queue tasks against a deck, approve the plan before anything runs, execute headless under budget caps, review results, and gate every outbound send — Dealer runs consume deck playbooks and file patch proposals back.
macOS required. API key secrets, OAuth client secrets, and OAuth tokens are stored in macOS Keychain. Linux and Windows are not supported for production use yet.
Requirements: Node.js 20+ · npm · Dashboard via agent-deck start / agent-deck open (listens on 127.0.0.1:1111) · Agent Deck MCP http://127.0.0.1:1110/mcp
1. Install and launch (managed install — auto-updates, keeps existing ~/.agent-deck data):
npx @agent-deck/cli@latest install
export PATH="$HOME/.local/bin:$PATH"
agent-deck start --daemon
2. Register Agent Deck in your agent (once per machine; <client> is codex, cursor, claude, or muse):
agent-deck setup --client <client>
Per-client details, restart and verify steps, and what setup installs: Agent harness.
3. Create a deck in the dashboard (My Decks → create a deck → drag cards from My Collection), or ask the agent in chat to create one.
4. Register playbooks (agent-first). Describe the procedure in chat — e.g. “Add a release checklist playbook with trigger ‘ship to npm’.” Let the agent register it and attach it to your deck.
5. Add external MCP servers and API keys (Linear, Notion, Slack, …) in the dashboard — OAuth in the browser, API keys pasted once into Keychain — then drag the cards onto your deck.
6. Pick a deck each session. Tell the agent which deck — “use the dev deck”, or mid-session “switch to my personal deck” — and approve the switch as This session only or This workspace by default. Or run agent-deck use <deck> in a repo so the deck binds on session open without naming it.
Same decks on another machine: keep ~/.agent-deck/ in a private Git repository you own, push and pull it yourself, then run agent-deck reindex — see Store format.
When you correct a playbook-driven result, Agent Deck turns the lesson into a reviewable patch proposal so future sessions start from what you taught it. Corrections become proposals you review in the dashboard (Playbook patches); accepted changes update the deck. Every run makes the next one better.
If you use per-repo use stubs and playbook triggers changed, refresh with agent-deck use --refresh.
To delegate a task to a local agent session on a deck, agent-deck run launches a signed-in client bound to that deck:
agent-deck run mydeck --client claude --cwd /path/to/repo --prompt-file ./brief.md --tools readonly
Per-client flags, resume, and trust behavior: DELEGATION.md.
The repo root is one plugin: one skills/ folder (agent-deck-session, agent-deck-playbooks, agent-deck-setup, agent-deck-run) plus .mcp.json, described by a manifest per client. Prerequisites for delegation: agent-deck >= 2.1.0 and the daemon running (see Quick Start), and the client CLI you delegate to, installed and signed in. The agent-deck-setup skill checks these and tells you what is missing.
Skills are never copied by hand: the muse copies come from root skills/ via scripts/copy-muse-skills.mjs at build time and agent-deck setup --client muse at install time.
npx @agent-deck/cli@latest install, agent-deck start --daemon, then agent-deck doctor.~/.cursor/plugins/local/agent-deck and run Developer: Reload Window). The plugin adds the four skills and the agent-deck MCP server (agent-deck mcp-launch, from .mcp.json); it needs the agent-deck CLI on PATH and stores no secrets.agent-deck open), then bind a project folder: agent-deck use <deck> --client cursor, and reload Cursor.agent-deck --version, agent-deck status, agent-deck deck list) and reports the result. Then try delegation: "Use agent-deck-run to have a read-only claude session on deck list the files in this folder, and report its answer." Expected: it launches agent-deck run <deck> --client claude --tools readonly --detach, polls agent-deck run status, and reports the session's answer with the runId and sessionId.agent-deck start --daemon
agent-deck open # re-open dashboard with a fresh auth cookie
agent-deck use <deck> # bind this folder to a deck
agent-deck export all -o backup.agent-deck.json
agent-deck credential list
agent-deck exec --connections cred_id -- <command>
agent-deck upgrade
agent-deck stop
Port conflicts: agent-deck status · agent-deck start --force. Full environment reference: Setup.
Index: docs/README.md · Security: SECURITY.md
MIT — see LICENSE.
Local MCP proxy — decks of tools, keys, and self-improving playbooks
{ "mcpServers": { "agent-deck-cli": { "command": "npx", "args": [ "-y", "@agent-deck/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@agent Deck/cli roda localmente via stdio.
Última verificação: 2026-11-20. Local MCP proxy — decks of tools, keys, and self-improving playbooks