aion-authoring-adk. The package 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
| Surface | How to reference it | When to use it |
|---|---|---|
| Global control plane | CapabilityReference.global_mcp() | Stable Aion tools such as tool search and execute. |
| Fixed capability | CapabilityReference.mcp(...) | Subject and key are known at setup time. |
| Runtime capability | RuntimeCapabilityReference.primary_mcp(...) | Subject is known after a request arrives. |
include_control_plane flag.
Add Aion MCP tools to an ADK agent
Useaion_adk_mcp_toolset when tools should be resolved per request.
- the fixed global control-plane 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.