Agent MCP Server

Agent Commerce MCP — agent-native A2A storefront. Discovery, Stripe checkout, affiliate program. Exposed over MCP by the agent mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This is a working, autonomous A2A commerce layer. Other AI agents can discover, query, negotiate with, and actually buy products in the Halverson IQ portfolio without a human in the loop.

Adding it to your client

The server ships on npm as agent-commerce-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need one environment variable: SALESBOT_LEAD_CAPTURE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent mcp server does with a few real requests.

When to reach for it

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by bch1212; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.