Agent MCP Server

Agent MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Local agent wallet + 900 pay-per-call data APIs — free discovery, x402 USDC, code-level spend caps.

What you get

On first run the server generates a wallet (standard BIP-39 phrase, imports into MetaMask/Rabby) and prints the address. Fund it with a few dollars of USDC on Base and paid calls just work. The recovery phrase is stored at ~/.pulsepay/wallet.json (file mode 600) — back it up. Prefer your own key? Set PULSEPAY_EVM_KEY and nothing is written to disk.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Agent is connected, these are the calls the assistant has available:

• pulse_discover — FREE
• pulse_call — pays the listed price
• pulse_balance — FREE
• pulse_report — FREE
• pulse_guardrail — FREE

Configuration and credentials

You will need one environment variable: PULSEPAY_EVM_KEY. 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.

Before you rely on it

• 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.

Choosing this one

Plenty of developer tooling 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. Agent's toolset — pulse_discover, pulse_call, pulse_balance and 2 more — is a fair guide to whether it matches your workflow. It is maintained by com.theaslangroupllc.pulse; 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.