npm · @cartpie/mcp · v1

Plug Cartpie into any AI agent.

The Cartpie MCP server gives Claude, Cursor, Windsurf and every other MCP-compatible client native tools for product extraction — one URL in, structured JSON out. Without writing a fetch call.

Get an API key Read the MCP docs

# requires Node 18+
npx -y @cartpie/mcp

# auth via env (create one in the dashboard)
export CARTPIE_API_KEY=cp_live_…

Tools exposed

Three primitives. Every product page on the web.

tool

extract_product(url: string)

Turn any retailer product URL into a normalized JSON object — title, price, currency, availability, variants, GTIN.

tool

extract_products(urls: string[])

Batch extraction. The agent passes an array of URLs; the server fans out and streams structured results back.

tool

find_offers(gtin: string)

Cross-retailer offer lookup by identifier. Compare prices and availability across every store we cover.

Drop-in config

Wire it into your client in 30 seconds.

Add a single block to your MCP client's config. Restart. Cartpie shows up in the tool palette — no rebuild, no deploy.

Create an API key first

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cartpie": {
      "command": "npx",
      "args": ["-y", "@cartpie/mcp"],
      "env": { "CARTPIE_API_KEY": "cp_live_…" }
    }
  }
}

Why MCP

The shortest path from your agent to the shelf.

Agent-native

No REST glue, no parsing, no schemas to maintain in the prompt — tools and arguments are typed at the protocol level.

Zero install

One npx line. The server runs on the user's machine and talks to Cartpie over HTTPS — no extra infra to deploy.

Same key. Same credits.

MCP calls bill against the same monthly credits as /v1. Cache hits and failures stay free, same as the REST API.

Give your agent a cart.

100 free credits to start. Same key works for REST and MCP.

Get API key MCP docs