MCP solves the tool interface
MCP gives agents a standard way to discover and call tools. That is a foundational capability for agent systems, but it does not define pricing, acceptance criteria, payment settlement or dispute records for paid work.
Accord adds those missing semantics without replacing MCP.
Accord adds the commercial record
When a tool call has economic consequences, the buyer needs a record of the requested work, the payment authority, the verifier and the settlement result. Accord's objects make that record explicit.
This is especially important when tools perform non-trivial work such as code review, research, data transformation or compliance checks.
The combined shape
In an Accord/MCP integration, MCP still handles the tool call. Accord wraps that call in agreement, verification and settlement data. The tool can stay focused on execution while the surrounding protocol records the lifecycle.
That separation makes implementations easier to inspect and safer to evolve.
FAQ
Does every MCP tool need Accord?
No. Accord is most useful when tool calls involve payment, acceptance criteria or settlement records.
Does Accord change the MCP protocol itself?
No. Accord/MCP is an integration layer around paid and verifiable tool calls.
Build a paid MCP tool
Wrap a tool call with agreement, payment and verification semantics.