resolve_dispute — agentic commerce MCP Tool Read-only
resolve_dispute
(resolve dispute) is one of 63 tools on the
agentic commerce
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_dispute from your client
- Claude Code agentic commerce resolve_dispute run in your project directory
- Claude Desktop agentic commerce resolve_dispute ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentic commerce resolve_dispute ~/.cursor/mcp.json
- VS Code agentic commerce resolve_dispute .vscode/mcp.json
- Zed agentic commerce resolve_dispute ~/.config/zed/settings.json
- Windsurf agentic commerce resolve_dispute ~/.codeium/windsurf/mcp_config.json
- Cline agentic commerce resolve_dispute ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentic commerce resolve_dispute ~/.gemini/settings.json
- Grok agentic commerce resolve_dispute .mcp.json (in your project root)
- ChatGPT agentic commerce resolve_dispute Settings → Connectors → Advanced → Developer mode
- Claude.ai agentic commerce resolve_dispute Settings → Connectors → Add custom connector
- LangChain agentic commerce resolve_dispute pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentic-commerce https://mcp.bosonprotocol.io/mcpOther tools on this server
- get_config_ids
- get_funds
- get_disputes
- get_dispute_by_id
- get_exchanges
- get_offers
- get_sellers
- get_dispute_resolvers
- create_offer
- create_offer_with_condition
- create_buyer
- sign_full_offer
- create_offer_and_commit
- create_offer_commit_and_redeem
- void_offer
- void_non_listed_offer
- void_non_listed_offer_batch
- create_seller
- update_seller
- send_signed_transaction
- send_meta_transaction
- send_native_meta_transaction
- send_forwarded_meta_transaction
- withdraw_funds
- deposit_funds
- extend_dispute_timeout
- expire_dispute
- expire_dispute_batch
- raise_dispute
- retract_dispute
- escalate_dispute
- decide_dispute
- refuse_escalated_dispute
- expire_escalated_dispute
- create_dispute_resolution_proposal
- revoke_voucher
- approve_exchange_token
- sign_receive_with_erc3009_authorization
- sign_receive_with_erc2612_permit
- sign_receive_with_permit2
- sign_receive_with_dai_permit
- commit_to_offer
- commit_to_conditional_offer
- commit_to_offer_and_redeem_voucher
- commit_to_conditional_offer_and_redeem_voucher
- commit_to_buyer_offer
- cancel_voucher
- redeem_voucher
- complete_exchange
- get_sellers_by_address
- get_all_products_with_not_voided_variants
- search_products
- validate_metadata
- store_product_v1_metadata
- store_bundle_metadata
- store_base_metadata
- render_contractual_agreement
- store_bundle_item_product_v1_metadata
- store_bundle_item_nft_metadata
- register_agent
- get_registered_agents
- get_supported_tokens
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.