MCP / agent stack

The agentic-commerce repo packages Boson as a Model Context Protocol server with ~56 tools, plus two ways to consume it: a typed TypeScript client and a GOAT SDK plugin.

Hosted endpoints

You don't have to run anything to start.

Env	URL
Staging	`https://mcp-staging.bosonprotocol.io/mcp`
Production	`https://mcp.bosonprotocol.io/mcp`

To run locally (stdio or HTTP):

npx @bosonprotocol/agentic-commerce boson-mcp-server

Three integration paths

1. GOAT SDK plugin (recommended for Vercel AI / LangChain / Claude)

import { bosonProtocolPlugin } from "@bosonprotocol/agentic-commerce"
import { getOnChainTools } from "@goat-sdk/adapter-vercel-ai"
import { viem } from "@goat-sdk/wallet-viem"
import { walletClient } from "./wallet"
 
const tools = await getOnChainTools({
  wallet: viem(walletClient),
  plugins: [
    bosonProtocolPlugin({
      url: "https://mcp-staging.bosonprotocol.io/mcp",
    }),
  ],
})
// `tools` now contains all 56 Boson tools, typed and ready to register with the model.

The plugin handles MCP transport, signs transactions through the wallet you pass in, and broadcasts. Fewest moving parts.

2. BosonMCPClient (typed TS client)

import { BosonMCPClient } from "@bosonprotocol/agentic-commerce/boson"
 
const client = new BosonMCPClient()
await client.connectToServer(
  "https://mcp-staging.bosonprotocol.io/mcp",
)
 
const unsignedTx = await client.createSeller({
  configId: "staging-84532-0",
  signerAddress: wallet.address,
  // ...
})
// You sign and broadcast yourself, via send_signed_transaction or your own wallet.

Use this when you want full control over signing and broadcasting — e.g. your wallet is in an HSM, in MPC custody, or behind a session-key manager. See Build for AI agents → Wallet patterns.

3. Raw MCP over HTTP

Any MCP-compliant client works (Claude Desktop, Cline, Cursor, etc.). Point it at the hosted URL and the tools appear in the model's tool registry. Signing is your responsibility.

What's in the tool catalogue

Category	Tools	Count
Seller & buyer	`create_seller`, `update_seller`, `create_buyer`, `get_sellers`, `get_sellers_by_address`, `get_dispute_resolvers`	6
Offer	`create_offer`, `create_offer_with_condition`, `sign_full_offer`, `create_offer_and_commit`, `void_offer` (+ batch + non-listed), `get_offers`, `get_all_products_with_not_voided_variants`, metadata helpers, `render_contractual_agreement`	13
Exchange	`get_exchanges`, `approve_exchange_token`, `commit_to_offer`, `commit_to_buyer_offer`, `complete_exchange`, `cancel_voucher`, `revoke_voucher`, `redeem_voucher`	9
Dispute	raise / resolve / retract / escalate / decide / refuse / expire (+ batch) / extend / create-proposal / read	13
Funds & meta-tx	`deposit_funds`, `withdraw_funds`, `get_funds`, `send_meta_transaction`, `send_native_meta_transaction`, `send_forwarded_meta_transaction`, `send_signed_transaction`	7
Agent registry	`register_agent`, `get_registered_agents`	2
Config	`get_config_ids`, `get_supported_tokens`	2

Full schemas and examples are in Reference → MCP tools.

Wallet management

The MCP server never sees private keys. State-changing tools return unsigned transactions; your client signs them. See Build for AI agents → The 3-step signing pattern for the canonical flow.

High-value asset module (Fermion)

A separate MCP server exposes tools for premium / fractionalized assets, with extra roles (verifier, custodian). See Build for AI agents → High-value asset module.

Quickstart → Buy with an AI agent — 5-minute hello-world.
Build for AI agents — patterns for autonomous buyer/seller agents.
Reference → MCP tools — every tool's schema, errors, and idempotency notes.