Catalogapi

What catalogapi MCP server does

The catalogapi MCP server exposes public CatalogAPI information to MCP-compatible assistants. It is intended for questions about international reward coverage, catalog contents, and the way the service operates. The server is read-only: it does not create orders, modify catalog data, or expose cart operations through MCP.

Its data comes from information already available through CatalogAPI's public browse experience. This makes it useful during product discovery, regional availability checks, and early integration research. Typical questions include whether rewards can be sent to specific countries, which reward categories are available in a market, and how fulfillment or catalog pricing works.

How it works

Clients connect over HTTP to the hosted MCP endpoint:

https://api.catalogapi.com/mcp

After connection, an assistant can select among four tools:

• check_coverage identifies covered countries and the categories available in each.
• search_rewards returns example items from the demonstration catalog for a selected country.
• get_reward_details provides information about one catalog item.
• how_it_works answers service-level questions about coverage, fulfillment, pricing, and integration.

The catalogapi MCP server does not require an API key, account, package installation, or local process. A client only needs MCP support and the hosted endpoint configuration. The repository includes a Claude Code command for adding the server over HTTP; instructions for other clients are referenced by the project but are not included in the supplied material.

Setup and configuration

Add the hosted server to Claude Code with:

claude mcp add --transport http catalogapi https://api.catalogapi.com/mcp

No environment variables are required for this MCP connection. The MCP service itself is separate from the CatalogAPI REST API and its Postman collection. The repository states that the REST API's sandbox workflow can use an API key, but that key is not needed for the read-only MCP server.

Limitations and notes

search_rewards is illustrative rather than an inventory query. It reads a demonstration catalog and does not return pricing, so its results should not be treated as a definitive statement of what a country supports. Use check_coverage for authoritative country and category coverage; if its result conflicts with a search result, prefer the coverage response.

The MCP tools expose only read operations. They do not provide the REST API's cart, catalog, or order lifecycle requests described in the repository's Postman collection. CatalogAPI is a commercial service, and the repository's MIT license applies to repository materials such as documentation and the collection—not to the service, API, or catalog data. Service and account questions are directed to CatalogAPI support, while MCP-server questions can be raised as repository issues.