Agentic Coding

Actionforge provides two MCP servers that let AI coding assistants build, run, and debug action graphs.

	What	How
☁️ Cloud MCP Server	Build and validate graphs locally	Remote MCP server
🖥️ Local MCP Server	Run and debug graphs locally	actrun mcp over stdio

Both MCP servers interact with graphs that you have stored locally on your computer. But the cloud MCP server is solely used for creating and editing them, and the Local MCP Server uses a local installation of actrun to run and debug these graphs.

☁️ Cloud MCP Server

The cloud MCP server gives AI agents the tools to create, validate, and explore Actionforge graphs. It connects to the Actionforge knowledge base for node search, documentation lookup, and example graph retrieval.

Endpoint: https://app.actionforge.dev/api/v2/mcp

Configuration

Claude Code

claude mcp add --transport http actionforge https://app.actionforge.dev/api/v2/mcp

Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "actionforge": {
      "url": "https://app.actionforge.dev/api/v2/mcp"
    }
  }
}

GitHub Copilot

Add to .vscode/mcp.json in your project:

{
  "servers": {
    "actionforge": {
      "type": "http",
      "url": "https://app.actionforge.dev/api/v2/mcp"
    }
  }
}

OpenCode

Add to opencode.json in your project:

{
  "mcp": {
    "actionforge": {
      "type": "remote",
      "url": "https://app.actionforge.dev/api/v2/mcp"
    }
  }
}

Windsurf

Add to your ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "actionforge": {
      "url": "https://app.actionforge.dev/api/v2/mcp"
    }
  }
}

Available Tools

Tool	Description
get_graph_schema	Full JSON schema for .act graph files
search_nodes	Search available node types by keyword or category
describe_node	Detailed documentation for a specific node type
get_node_schema	Full JSON schema for specific node types
get_port_types	Port data types and connection rules
validate_graph	Validate a complete graph structure
search_graph_examples	Find example graphs and recommended nodes for a task
search_documentation	Search the Actionforge knowledge base (CLI docs, API references, general docs)

🖥️ Local MCP Server (actrun)

The actrun CLI includes a built-in MCP server for running and debugging graphs locally. It communicates over stdio and exposes debug tools that let an AI agent step through graph execution node by node, set breakpoints, and inspect state.

Tip

Install actrun first. See the Installation guide.

Configuration

Claude Code

claude mcp add actrun -- actrun mcp

Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "actrun": {
      "command": "actrun",
      "args": ["mcp"]
    }
  }
}

GitHub Copilot

Add to .vscode/mcp.json in your project:

{
  "servers": {
    "actrun": {
      "command": "actrun",
      "args": ["mcp"]
    }
  }
}

OpenCode

Add to opencode.json in your project:

{
  "mcp": {
    "actrun": {
      "type": "local",
      "command": ["actrun", "mcp"]
    }
  }
}

Windsurf

Add to your ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "actrun": {
      "command": "actrun",
      "args": ["mcp"]
    }
  }
}

Available Tools

Tool	Description
debug_connect	Connect to a local actrun debug server
debug_run	Send a graph and start execution
debug_step	Step over the current node
debug_step_into	Step into a group node
debug_step_out	Step out of a group node
debug_resume	Resume until breakpoint or completion
debug_pause	Pause at the next node
debug_set_breakpoint	Set a breakpoint at a node
debug_remove_breakpoint	Remove a breakpoint
debug_inspect	Inspect current debug state
debug_logs	Retrieve buffered log output
debug_stop	Stop the current execution
debug_disconnect	Close the debug connection

Debug Workflow

The AI agent follows this flow automatically:

1. Start actrun --local in the background (captures the WebSocket port)
2. Call debug_connect with the port
3. Read the .act file from disk and send it via debug_run
4. Step through execution with debug_step / debug_step_into / debug_resume
5. Inspect state and logs at each pause point
6. Call debug_disconnect and stop the background process when done