# How to Customize MCP Server Configuration per Workflow Node in Archon

> Customize MCP server settings per workflow node in Archon. Inject unique configurations into Claude SDK instances by defining an optional mcp field in your workflow node.

- Repository: [Cole Medin/Archon](https://github.com/coleam00/Archon)
- Tags: how-to-guide
- Published: 2026-04-10

---

**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