Search merchants, inspect structured offers, and validate checkout or negotiation before buying.
Search merchants, inspect structured offers, and validate checkout or negotiation before buying. The nexez agentic commerce mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
Nexez is the infrastructure layer for agentic commerce. Businesses create clean, structured agent-ready listings alongside their main website. AI agents (ChatGPT, Claude, Grok, Perplexity, etc.) can discover offers, negotiate, and complete bookings autonomously.
Everything the assistant can do here goes through one of these:
Agent — optimized listings** with JSON-LD, llms.txt, agent.json, MCP endpoint, and semantic HTMLReal — time agent detection and traffic splitProduction — ready error handling, logging, and webhooksCopy — paste buyer-agent examples in examples/agentsFrontend — Next.js 16 (App Router) + Tailwind + shadcn/uiBackend — Next.js API routes + SupabaseDatabase — Supabase (PostgreSQL)Payments — Stripe Connect + Stripe BillingDeployment — VercelCore — The Core tool exposed by this serverTechnical — The Technical tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @nexez/agent-sdk on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nexez Agentic Commerce's toolset — Agent, Real, Production and 8 more — is a fair guide to whether it matches your workflow. It is maintained by ai.nexez; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Agent | optimized listings** with JSON-LD, llms.txt, agent.json, MCP endpoint, and semantic HTML |
| Real | time agent detection and traffic split |
| Production | ready error handling, logging, and webhooks |
| Copy | paste buyer-agent examples in examples/agents |
| Frontend | Next.js 16 (App Router) + Tailwind + shadcn/ui |
| Backend | Next.js API routes + Supabase |
| Database | Supabase (PostgreSQL) |
| Payments | Stripe Connect + Stripe Billing |
| Deployment | Vercel |
| Core | The Core tool exposed by this server. |
| Technical | The Technical tool exposed by this server. |
{
"mcpServers": {
"commerce": {
"command": "npx",
"args": ["-y", "@nexez/agent-sdk"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.