The CrossUp MCP

The CrossUp MCP gives your agent the SDK’s two reads: read a catalog item and request a recommendation. It runs on your machine, over stdio, with the storefront key in an environment variable. It doesn’t write: an MCP is driven by a model, and a write triggered by a hallucination can’t be undone.

The tools

Tool	What it does	Input
`get_catalog_item`	The canonical aggregate of an item: item, variants, availability	`{ item_id }`
`get_recommendations`	A recommendation for a moment, with each result already projected onto the catalog	`{ connection_id, surface, placement_key, context_item_id?, cart_items? }`

Both return the same as the API, with the same typed errors. A results: [] comes with its reason_codes.

Connect it

The server is called crossup-salespilot. It needs CROSSUP_API_TOKEN (the spk_… key) and, if it isn’t the public URL, CROSSUP_BASE_URL.

Claude Code
Claude Desktop
Cursor

claude mcp add crossup-salespilot \
  -e CROSSUP_API_TOKEN=spk_… \
  -e CROSSUP_BASE_URL=https://salespilot.crossup.ai \
  -- bun run <path-to-repo>/apps/mcp-server/src/index.ts

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "crossup-salespilot": {
      "command": "bun",
      "args": ["run", "<path-to-repo>/apps/mcp-server/src/index.ts"],
      "env": {
        "CROSSUP_API_TOKEN": "spk_…",
        "CROSSUP_BASE_URL": "https://salespilot.crossup.ai"
      }
    }
  }
}

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "crossup-salespilot": {
      "command": "bun",
      "args": ["run", "<path-to-repo>/apps/mcp-server/src/index.ts"],
      "env": {
        "CROSSUP_API_TOKEN": "spk_…",
        "CROSSUP_BASE_URL": "https://salespilot.crossup.ai"
      }
    }
  }
}

Today it runs from the repository, with bun. An installable package and a remote server with your CrossUp account, without pasting a key, come later: see below.

Without a key the server starts anyway and both tools respond configuration_error: CROSSUP_API_TOKEN is not set: the agent sees why it fails.

This documentation’s MCP

This documentation has its own MCP server at /mcp: an agent searches and reads any page without you pasting it. It is a separate server: one reads the docs, the other talks to the API.

claude mcp add --transport http crossup-docs https://docs.crossup.ai/mcp

What’s next

Step	What it adds	What it needs
Signals and `doctor`	`record_storefront_signals`, and a `doctor` that tests key, quota and a recommendation	The same key
Context	Resources with the full docs and integration prompts	Nothing: these docs
Operate	Analytics, enabling moments, rotating keys	An admin credential
Installable from Claude	A remote server with OAuth and your account	The above

What you will see

In your agent, two new tools under crossup-salespilot. Ask it “fetch item itm_… from the catalog” and it has to return the aggregate with variants and availability.

If you don’t see it

What happens	What to do
`configuration_error`	`CROSSUP_API_TOKEN` is missing from the server’s `env`, or was left empty
`401` on every tool	The key is revoked or badly copied
The server shows as “down” in the UI	`bun` is missing, or the path to the repo isn’t right. Run the command by hand in a terminal

llms.txt

All the documentation in one file.

The CLI

The same two reads, for a person.

​The tools

​Connect it

​This documentation’s MCP

​What’s next

​What you will see

​If you don’t see it

llms.txt

The CLI

The tools

Connect it

This documentation’s MCP

What’s next

What you will see

If you don’t see it