MCP connects tools. Accord adds work semantics.
The Model Context Protocol gives agents a way to discover and call tools. That solves a major interoperability problem, but it does not define how a tool should price work, verify completion or record settlement.
Accord/MCP sits around the tool call. It can bind a request to an Agreement Object, require payment or payment authority, run the handler, invoke verification and emit receipts.
Why paid tools need more than access control
A paywalled tool can charge for access, but many agent tasks are outcome-oriented. A buyer may care less about whether a request was served and more about whether the promised analysis, audit, transformation or report met the agreed acceptance criteria.
Accord/MCP gives tool builders a protocol vocabulary for that distinction.
Start with the mock rail
The recommended first run is the paid MCP repository audit example. It exercises the lifecycle without real funds, chain state or facilitator trust. That makes it appropriate for developers who want to understand Accord before touching testnet rails.
Only after the lifecycle is clear should teams move toward rail-specific testnet experiments.
FAQ
Does Accord/MCP require real payments?
No. The mock rail demo runs the lifecycle without real funds.
Can any MCP tool use Accord?
In principle yes, but useful integration depends on pricing, verification and policy design.
Run the paid MCP demo
Start with the mock rail repository audit before any testnet work.