Standalone and MAMS Integrations
Use the same reasoning architecture in a standalone ASTRA application or in a MAMS service. The difference is where the protocol infrastructure lives.
Component |
Standalone application |
MAMS application |
|---|---|---|
Reasoning, tools, memory and capability contracts |
|
|
Protocol infrastructure |
|
|
HTTP and protocol lifecycle |
Standalone adapters |
CArtAgO resource-backed adapters |
Native callable goals |
ASTRA plans |
ASTRA plans |
mams-astra-llms supplies alternatives to the standalone tools artifact. Select the modules explicitly; adding the dependency does not automatically replace module declarations in an existing agent.
Choose the MAMS modules
Integration |
MAMS module |
|---|---|
MCP |
|
UTCP |
|
A2A |
|
OpenAPI |
|
Discovery |
|
The MCP and UTCP reasoning subclasses are mams.llms.mcp.ReActMCP and mams.llms.utcp.ReActUTCP. They supply remote execution hooks while sharing ReActTools reasoning. ReActCapabilities can bind MAMS MCP and UTCP instances through instance().
Resource ownership
MAMS MCP sessions are owned by session artifacts. UTCP and OpenAPI use explicitly attached HTTP artifacts. For A2A, passive card resources describe the service, active task resources permit native request decisions, and outbound exchange artifacts perform client interaction.
These resources give the agent observations and operations through its work environment. They do not move reasoning into the HTTP implementation. Existing passive or active endpoint policies continue to apply to calls made through UTCP descriptions.
Current boundaries
The resource-backed A2A profile supports fresh JSON-object tasks over JSON-RPC with polling, progress, lookup and cancellation. Streaming, push notifications, task continuation and durable task storage are not implemented. Do not assume it has the same profile as an older standalone A2A walkthrough.
Start with the separate MAMS examples: mams-mcp, mams-utcp, mams-a2a, mams-capabilities, mams-openapi-capabilities and mams-discovery. For resource creation and request policies, read the MAMS guide. The integration README describes the resource wiring and supported profiles.