Connect Cursor or Claude Desktop to PayAPI’s MCP server

When an agent needs a data source, hard-coding a catalogue of API names into a project is brittle. A marketplace search server offers another route: connect an MCP client, ask it to find relevant listings, then decide whether to call one. PayAPI Market provides a free, read-only MCP search server at https://payapi.market/mcp. The marketplace lists Cursor and Claude Desktop among compatible clients.

The useful distinction is between discovery and execution. The MCP server lets a client search, list and get marketplace information. It does not, by itself, make a paid API call. PayAPI’s listings use per-request payments in USDC on Base, without requiring keys or signups. Payment happens when an agent calls a listing’s API, not while searching the catalogue.

Connect the server

1. Open the MCP server configuration for your client. Use the client’s own instructions for adding a remote MCP server; the exact configuration fields depend on the client and its version.

2. Add PayAPI Market as a server and use this address: https://payapi.market/mcp. The server is read-only and free to search. PayAPI says marketplace discovery does not require a key or signup.

3. Save the configuration and follow the client’s normal process for making a newly added MCP server available. If the client asks for connection details beyond the server address, check its current MCP instructions rather than guessing at a transport or copying a configuration from a different client.

PayAPI does not publish a single configuration recipe here that applies to every client. That matters in practice: a snippet intended for one version or connection method can fail in another. Cursor and Claude Desktop are both listed as compatible, but use each client’s own setup path.

Search before you call

Once connected, ask the client to search PayAPI Market for the task and the kind of data you need. A concrete prompt is more useful than a broad one: name the subject, geography or input type, and the result you expect. For example, ask for an API that can look up a UK postcode and return an address, rather than asking only for “a location API.”

Inspect the results before calling anything. Check what the listing says the endpoint does, what input it expects, and the listed price. PayAPI’s marketplace includes APIs across areas such as property, company information, weather and vehicles. Sample prices range from $0.001 to $0.002 per request, but the actual listing is what matters for a particular call.

Search results are discovery, not a guarantee that a service fits your code. Confirm that the endpoint can supply the fields your task needs. If the catalogue returns no match, tighten or change the search terms; do not treat an empty result as evidence that no provider offers the data anywhere.

Understand the payment boundary

The MCP server is read-only. Finding a listing does not purchase data or trigger a paid API request. A separate call to a listing’s endpoint is where the x402 payment flow applies. PayAPI describes the marketplace model as agents paying per request in USDC on Base, with no API keys or signup required. Keep that boundary clear when designing an agent: discovery can inform a decision, while calling a paid endpoint is an action with a per-request cost.

For a workflow that should stay within a budget, have the agent inspect the listing and price before it calls the endpoint. Make the allowed task and acceptable cost explicit in the workflow. The marketplace provides the listing information; the application still needs to decide when a discovered service is appropriate to call.

Use verification as one signal

PayAPI distinguishes settlement-verified listings from listings that have only responded to a challenge. Its settlement-verified badge is confirmed through test wallet transactions. Treat that as evidence about a tested payment and response, not as a guarantee that an endpoint will meet every project’s data, uptime or output requirements. Check the listing against the job you are asking the agent to do.

PayAPI Market is also listed in the official MCP Registry as market.payapi/marketplace. That gives teams another way to identify the server, but the connection address for this walkthrough remains https://payapi.market/mcp.

The practical pattern is simple: connect once, search when the task calls for a capability, inspect the listing, and make the paid call only when it fits. That keeps endpoint discovery out of local key management while leaving the decision to spend with the agent workflow that uses the API.