Menu
Connect agents to Context7, package-version, sequential-thinking, memory, GitHub MCP servers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Authoring policy for producing Office documents (xlsx/pptx/docx) as `document` subjects. Used by the author-document workflow's generate phase — draft a spec, render+store via the animus-document-engine store_document tool, then record it with create_subject.
Operate Animus v0.7 execution environments — environment plugins and coder nodes, the cross-phase environment broker, workflow/phase `environment:` pinning, `environment_routing:` rules, `workspaces:` multi-repo checkout sets, lease records and the startup reaper, and animus-environment-railway. Use when pinning workflows to remote execution, debugging node acquisition or teardown, or authoring multi-repo runs.
Operate the Animus portal (animus-launchapp) — the flat-named portal MCP surface and admin-only tool visibility, Claude/Codex subscription Connections, the external MCP-server catalog with Connect handshake and ext.* subject projection, the durable script registry and phase_context_schema authoring loop, team_* workflow authoring over MCP, and trigger-event observability. Use when driving a portal deployment rather than a local CLI install.
Product lifecycle agents — product owner, architect, auditor, docs-writer, devops, researcher personas
Guide a project from idea to autonomous engineering setup — interview the user, write VISION.md, AGENT_PRINCIPLES.md, registry, agents/workflows/phases/schedules YAML, scripts, and a first runnable task. Use when standing up Animus in a new project beyond the minimal /animus-setup scaffold.
Set up .mcp.json, Claude Code permissions, and connect AI tools to Animus's MCP server
| name | animus-mcp-servers-for-agents |
| description | Connect agents to Context7, package-version, sequential-thinking, memory, GitHub MCP servers |
| user_invocable | false |
| auto_invoke | true |
| animus_version | 0.7.0-rc.18 |
Animus agents can connect to external MCP servers beyond the built-in animus server. This gives agents access to documentation lookup, package version checking, structured reasoning, persistent memory, and GitHub operations.
mcp_servers: keyServers go in .animus/workflows.yaml or any .animus/workflows/*.yaml file:
mcp_servers:
context7:
command: npx
args: ["-y", "@upstash/context7-mcp"]
package-version:
command: npx
args: ["-y", "mcp-package-version"]
sequential-thinking:
command: npx
args: ["-y", "@modelcontextprotocol/server-sequential-thinking"]
memory:
command: npx
args: ["-y", "@modelcontextprotocol/server-memory"]
github:
transport: http
url: https://api.githubcopilot.com/mcp/
oauth:
flow: manual_bearer
bearer_env: GITHUB_MCP_TOKEN
(The @modelcontextprotocol/server-github npm package is deprecated
upstream — use GitHub's hosted MCP endpoint, as the OAuth example later in
this skill does.)
Each entry picks exactly one transport via transport::
stdio (default when omitted) — requires command:; optional args: and env:. url must not be set.http — requires url: (an http:// or https:// endpoint). command, args, and env must not be set.mcp_servers:
my-remote:
transport: http
url: https://mcp.example.com/mcp
Optional per-server fields: config: (arbitrary key-value config passed to the server) and tools: (declared tool-name list — schema-validated but not currently enforced as a runtime filter, so don't rely on it to restrict access).
Secrets in env: blocks: use ${VAR} interpolation (${VAR:-default}, ${VAR:?error}) rather than literal values. Resolution checks the process environment first, then OS keychain entries set via animus secret set <KEY> (preferred for credentials).
agents:
implementer:
mcp_servers: ["animus", "context7"]
researcher:
mcp_servers: ["animus", "context7", "package-version", "memory"]
reviewer:
mcp_servers: ["animus", "github", "sequential-thinking"]
Agents only get access to the servers listed in their mcp_servers array.
The resolved server set is passed down to the provider plugins themselves:
it rides the provider contract for animus agent run and animus chat to
any provider plugin that declares supports_mcp (manifest field, plugin
protocol 1.2.0; undeclared defaults true), and on the workflow path via
workflow-runner v0.4.3+. Secret-bearing servers (all OAuth flows) are
rewritten to animus-mcp-proxy stdio entries before pass-down — tokens
never reach CLI configs or argv. The name animus always resolves to the
built-in animus mcp serve stdio surface.
For deterministic, LLM-free access from scripts and command phases, use
animus mcp tools <server> (list) and
animus mcp call <server> <tool> --args '<json>' (v0.7.0-rc.9+) — OAuth
servers route through the proxy with the bearer injected, never printed.
Tell agents what tools are available and when to use them:
implementer:
system_prompt: |
TOOLS: You have access to context7 MCP tools. Before writing code
that uses external libraries, use resolve-library-id and
get-library-docs to look up the CURRENT API.
http servers can carry an oauth: block. Flows: authorization_code (interactive browser login via animus mcp auth <server>), client_credentials, refresh_token, manual_bearer. Credential material is read from env vars via *_env fields (client_id_env, client_secret_env, refresh_token_env, bearer_env), never from YAML. Other fields: token_url, scopes, audience, cache (default true), and — for authorization_code providers without Dynamic Client Registration — a pre-registered client_id plus client_secret_env for confidential clients (v0.7.0-rc.12+; resolved from process env, then the animus secret keychain).
mcp_servers:
github:
transport: http
url: https://api.githubcopilot.com/mcp/
oauth:
flow: authorization_code
scopes: [repo, read:user]
CLI: animus mcp auth <server> (login), animus mcp auth-status, animus mcp auth-logout <server>. Full shape and validation rules: docs/reference/mcp-oauth.md in animus-cli.
Top-level phase_mcp_bindings attaches servers to specific phases (mainly used by pack overlays):
phase_mcp_bindings:
research:
servers: [context7]
Server names must resolve against the mcp_servers: map. See the pack-authoring docs for how packs ship these.
Skills are a third attachment path (v0.5.14): a skill definition can declare mcp_servers, and when a workflow phase's skills: (or the executing agent profile's skills:) resolve and apply, the skill's declared servers join the phase contract the same way phase_mcp_bindings do — resolved by name against the mcp_servers: map; unknown names warn and are skipped.
animus agent run and animus chat send resolve the server set as: the
--agent profile's mcp_servers ∪ the --skill's mcp_servers ∪
--mcp-server <name> additions (repeatable; the name must exist in the
project's mcp_servers map, or animus for the built-in surface), minus the
built-in animus server when --no-animus-mcp is passed. When no profile or
skill names any server, the baseline set is just the built-in animus server.
A tool whose CLI cannot speak MCP receives no MCP wiring.
@upstash/context7-mcp) — HIGH priorityUp-to-date, version-specific library documentation. Prevents hallucinated APIs.
Tools: resolve-library-id, get-library-docs
Best for: implementer, architect, docs-writer, researcher
Why: LLM training data goes stale. React Router 7, Hono, Drizzle, and Better-Auth all move fast. Context7 gives agents current docs instead of guessing.
mcp-package-version) — MEDIUM priorityChecks latest stable versions from npm registry.
Tools: Check npm/PyPI/Maven/Go versions, bulk check multiple packages.
Best for: researcher, auditor
Why: Prevents agents from adding outdated dependency versions.
@modelcontextprotocol/server-sequential-thinking) — MEDIUM priorityHelps agents break down complex problems step by step.
Best for: architect (dependency graphs), product-owner (feature evaluation), reviewer (code review), auditor (security analysis)
Why: Complex reasoning tasks benefit from structured step-by-step thinking.
@modelcontextprotocol/server-memory) — MEDIUM priorityPersistent memory across agent runs. Agents can remember what they reviewed last time.
Best for: planner, researcher, scanner, product-owner, architect, reconciler
Why: Without memory, each cron run starts from scratch. The PO can't remember what it reviewed, the researcher re-checks the same packages, the reconciler re-analyzes the same tasks.
@modelcontextprotocol/server-github) — LOW priorityStructured GitHub operations as MCP tools.
Best for: planner, reviewer, reconciler
Why: Mostly redundant with gh CLI (already in tools_allowlist). Useful for structured PR data (reviews, checks, mergeable status) without parsing CLI output.
animus ctx7 pkg-ver seq-think memory github
planner x x x
implementer x x
reviewer x x x
researcher x x x x
scanner x x
product-owner x x x
architect x x x x
auditor x x x
docs-writer x x
reconciler x x x
devops x
MCP server tools are separate from the tools_allowlist. The allowlist controls which shell programs command phases can invoke. MCP tools are controlled per-agent via the mcp_servers binding.
To enable web search for agents, add to tools_allowlist:
tools_allowlist:
- WebSearch
- WebFetch