A Model Context Protocol (MCP) integration connects an MCP-compatible AI host to external tools, resources, or workflows through the open MCP standard.
In AI commerce, MCP can expose offer-search tools, but it does not define the commercial data or revenue model itself. AON uses MCP as a host-to-tool path, while AgentOffer Protocol and delivery contracts define the meaning of commercial intent, Offer objects, actions, Goals, and attribution.
AON’s MCP integration
AON exposes an authenticated JSON-RPC endpoint at /v1/mcp for compatible hosts with provisioned access. The current Hosted MCP production certification covers the exact five-tool projection documented in Docs, while the connected server’s tools/list response remains the authority for current names and schemas. Runtime certification belongs to the deployment owner and does not certify REST, OpenAPI, SDK, or Portal surfaces.
Typical MCP integration flow
Connect an MCP-compatible host
The host is configured with the AON MCP endpoint and a Bearer API key under the host’s own permission model.
Discover available tools
The host uses MCP initialization and tools/list to read the capabilities and input schemas exposed by the current server.
Call a commerce tool
The host invokes an available tool with the user’s current request and only the supported context defined by that tool schema.
Evaluate and present results
The host decides whether and how to present a returned Offer and preserves the documented action and attribution path when the user continues.
What an AON MCP integration needs
MCP provides the connection. A working commercial integration also needs AON access, the active tool schemas, and a host product that decides how to use the result.
| Concept | Meaning |
|---|---|
| Provisioned access | Configure an MCP-capable host with the /v1/mcp endpoint only after MCP access has been provisioned for the account and the required API key is available. |
| The active tool schema | Use tools/list to confirm the available tool names and inputs instead of relying on a stale tool list or invented fields. |
| The five-tool runtime | The current Hosted MCP projection exposes aon_search_offers, aon_resolve_category, aon_get_category_schema, aon_submit_feedback, and aon_manage_watch; a connected deployment may publish a different surface. |
| A product decision | The host product decides whether a returned Offer helps the user, how it is presented, and whether the documented action and attribution path are used. |
- MCP connectivity does not authorize inferred or unrestricted user context. The host should send only what the active tool schema and its own permission model support.
- Protocol publication or a Hosted MCP certification does not grant account access and does not certify another AON surface or deployment.
MCP vs AgentOffer Protocol
MCP standardizes the connection between an AI host and external capabilities. AgentOffer Protocol standardizes the commercial information exchanged for offer discovery and attribution. An implementation can use both: MCP for tool access and AgentOffer contracts for the meaning and structure of the commerce data. See the AgentOffer Protocol definition.
Example in practice
A research assistant running in an MCP-compatible host receives a request for team accounting software. The host can use available category guidance before searching for offers, evaluate the returned results, and present a suitable option in its own interface while preserving the documented action and attribution path.
Common questions about model context protocol (mcp) integration
Do I need provisioned AON access and an API key to use the MCP integration?
Yes. MCP is the connection from a compatible host to a tool; it does not by itself grant a live AON account, offer access, or credentials. The account must have MCP access provisioned, and the host needs the /v1/mcp endpoint plus the authentication configuration required for its environment.
Who controls presentation in an MCP integration?
The host retains its product and rendering decisions, subject to the documented Offer action, attribution, and disclosure requirements.
What context should an MCP host send to an offer-search tool?
Send intent.content plus the optional documented fields your integration has, such as explicit current-turn signals and session identifiers. Omit the whole budget signal if its currency is unknown, and use aon_resolve_category rather than inventing taxonomy IDs. Use the active tool schema as the authority for supported inputs.
What is the current Hosted MCP tool surface?
The current Hosted MCP production certification covers five tools: aon_search_offers, aon_resolve_category, aon_get_category_schema, aon_submit_feedback, and aon_manage_watch. Use the active server’s tools/list response as the authority for the connected runtime, and follow the integration guide for endpoint and credential requirements.
Sources
- AON integration guideAON documentation
- AON Claude integrationAON documentation
- Model Context Protocol specificationPrimary standard
- Model Context Protocol architecturePrimary standard