MCP tool pattern

Expose WATP as commerce tools for AI applications.

MCP gives agents structured access to tools and context. WATP can be the tool-backed negotiation runtime behind actions like supplier discovery, start negotiation, counteroffer, conclude, and retrieve audit trail.

WATP endpoints usable todayMCP adapter patternNo official MCP server shipped yet

MCP owns

Tool discovery and invocation

An MCP host can decide which tools an AI application may call and what context is exposed to that model.

WATP owns

Signed commerce negotiation

The actual B2B state machine stays in WATP: signed messages, replay protection, idempotency, hash chain, and handoff payload.

Today

Builders can wrap WATP now

A developer can wrap the live WATP APIs or SDK helpers in MCP tools today. The WATP project is not claiming a public official MCP server package yet.

Practical flow

1.

Expose watp.discover_suppliers to the MCP host.

2.

Start a WATP negotiation with signed credentials.

3.

Let the agent propose, counter, or request human approval.

4.

Return final terms and the audit chain to the application.

What this does not claim

MCP is not a checkout protocol and does not replace the negotiation state machine. WATP can sit behind MCP tools, but WATP still needs its own node credentials, HMAC or Ed25519 validation, idempotency, and registry trust rules.

tools:
  watp.discover_suppliers
  watp.start_negotiation
  watp.conclude