Skip to main content
Aion supports LangGraph MCP access through aion-authoring-langgraph. The package builds on aion-mcp and returns standard LangChain MCP adapter configuration or LangChain-compatible tools. Use MCP in LangGraph when your agent needs tools exposed by the Aion control plane or by a runtime capability, such as the MCP server attached to the distribution that delivered the request.

MCP surfaces

The global control-plane MCP server is now just an explicit capability reference in the list. There is no separate include_control_plane flag.

Load tools inside a graph node

Use this pattern when tool availability depends on the incoming request.
CapabilitySubjectSource.INCOMING_DISTRIBUTION means the incoming request distribution from the Aion Distribution extension payload. It is resolved from the current request’s AionRuntimeContext, not from global process state.

Build a MultiServerMCPClient config

LangChain’s MCP adapter accepts a mapping of server names to transport config. Aion can generate that mapping with authenticated headers.
The generated server entries use:

Fixed capability reference

Use a fixed reference when the endpoint is known at setup time.
Fixed references do not require a runtime context unless you also pass runtime_capability_references. Pass an explicit principal_selector when no runtime context is available and the endpoint must be scoped to a runtime principal.

Runtime primary capability

Use runtime references when a graph can be reused across projects or invoked through different distributions.
This means: when this request arrives, take the distribution from the request payload and connect to that distribution’s primary MCP capability. For agent or environment-specific tools, use another source: