how-to-guide

How to Customize MCP Server Configuration per Workflow Node in Archon

April 10, 2026 coleam00/Archon ↗

Archon enables per-node MCP customization by accepting an optional mcp field in workflow node definitions, which points to a JSON configuration file that is validated, loaded with environment variable expansion, and injected into Claude SDK instances while being ignored for Codex providers.

Archon's workflow engine supports fine-grained Model-Context-Protocol (MCP) server management by allowing individual DAG nodes to specify their own proxy configurations. This architecture, implemented in the packages/workflows directory, lets developers isolate tool permissions and server environments to specific steps rather than applying global settings. The system

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:

curl -s "https://instagit.com/install.md"

Add to your MCP client configuration:

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}

Ask your agent:

"Use Instagit MCP to understand how coleam00/Archon works."

Works with

Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →