aion.adk.authoring, which builds on aion.mcp
and returns ADK toolsets backed by Aion-authenticated MCP endpoints.
Use MCP in ADK 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
Each surface is passed as a capability reference in the same list, the built-in metatools server
included.
Add Aion MCP tools to an ADK agent
Useaion_adk_mcp_toolset when tools should be resolved per request.
- the built-in metatools MCP server
- the primary MCP server for the current incoming request distribution
- bearer auth and principal selector headers for the request
Supplying runtime context
Runtime references need the currentAionRuntimeContext. The ADK helper uses
default_adk_runtime_context to read it from the ADK readonly context:
context_provider:
CapabilitySubjectSource.INCOMING_DISTRIBUTION means the incoming request distribution from the
Aion Distribution extension payload. It is resolved from the current request context, not from
global process state.
Fixed capability reference
Use a fixed reference when the endpoint is known before the request is handled.principal_selector when no runtime context is available and the endpoint must be
scoped to a runtime principal.
Direct McpToolset instances
If the runtime context is already available in setup code, use the synchronous helper to create
direct ADK McpToolset instances.