MCP Server

Model Context Protocol integration

MCP Server (Model Context Protocol)

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

AIWG includes an MCP server for programmatic integration with AI tools.

The AIWG MCP Daemon is listed in the mcpservers.org directory.

Quick Start

Use AIWG to complete this documented outcome: Quick Start
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Available Tools

Tool	Description
`discover`	Search AIWG skills, agents, commands, rules, flows, runbooks, templates, and behaviors
`skill-list` / `skill-show`	List skills and fetch full SKILL.md bodies
`command-list` / `command-show`	List CLI commands and fetch command definitions
`rule-list` / `rule-show`	List rules and fetch rule bodies
`agent-list` / `agent-show`	List agents and fetch agent definitions
`template-list` / `template-show` / `template-render`	List, fetch, and render templates
`command-run`	Run allow-listed `aiwg` CLI commands
`artifact-read`	Read artifacts from .aiwg/ directory
`artifact-write`	Write artifacts to .aiwg/ directory

Opt-in toolsets add Flow, Mission, memory, knowledge-base, research, activity-log, index, Ralph, Mission Control, ops, and Agentic Sandbox tools:

Use AIWG to complete this documented outcome: Opt-in toolsets add Flow, Mission, memory, knowledge-base, research, activity-log, index, Ralph, Mission Control, ops, and Agentic Sandbox tools
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

The `sandbox` toolset exposes revisioned fleet inventory/admission/observation/ reconciliation and governed activity coverage/timeline/export. Configure it with `AIWG_SANDBOX_MANAGEMENT_URL` and a mode-`0600` bearer file named by `AIWG_SANDBOX_MANAGEMENT_TOKEN_FILE`. Credentials are server configuration, never tool inputs or outputs. Non-loopback endpoints must use HTTPS. Mutations and evidence export require `confirmed: true`; unsupported upstream endpoints return a typed `supported: false` result for HTTP 404/405.

`workflow-run` has been removed from the core MCP surface. Use `command-run` for general CLI execution, the `flows` toolset for `flow-list` / `flow-show` / `flow-run`, or the `missions` toolset for Mission guide, dispatch, and status.

Available Prompts

Prompt	Description
`decompose-task`	Break down complex tasks into steps
`parallel-execution`	Plan parallel agent workflows
`recovery-protocol`	Handle workflow failures

These prompts are auto-integrated and available in compatible tools.

Configuration

Claude Desktop

After running the agent-owned mcp operation, the config is placed in:

macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
Linux: `~/.config/Claude/claude_desktop_config.json`

Cursor

After running the agent-owned mcp operation, the config is added to your Cursor settings.

Manual Configuration

If automatic installation doesn't work, add this to your MCP config:

{
  "mcpServers": {
    "aiwg": {
      "command": "aiwg",
      "args": ["mcp", "serve"]
    }
  }
}

Technical Details

Transport: stdio (standard input/output)
Protocol Version: MCP 2025-11-25
Implementation: TypeScript with @modelcontextprotocol/sdk