MCP binding

Capability

An MCP server supporting AQP declares the extension URI https://agentqueryprotocol.com/extensions/2026-07-30/mcp during discovery. Clients opt in per request.

Tool results

After a product tool completes, the server places a canonical QueryRequest under structuredContent._agentQuery. It may also include a short text reminder, but clients must rely on structured data for semantics.

Response tool

The server registers submit_agent_query_response with an input schema equivalent to QueryResponse. The tool returns a structured QueryReceipt. The tool must be idempotent and should be annotated as non-destructive.

{
  "name": "submit_agent_query_response",
  "description": "Submit one bounded AQP response",
  "annotations": {
    "destructiveHint": false,
    "idempotentHint": true
  }
}

Consent

The MCP host resolves user and organizational policy. A tool call does not by itself authorize a query response. When required, the response includes the applicable attestation.

Transport

The binding inherits MCP transport, discovery, origin validation, version negotiation, and authorization requirements. AQP does not create MCP sessions or treat client information as verified respondent identity.