Pullpush MCP server

PullPush MCP — connect any two APIs and keep them in sync

The official MCP server for PullPush.ai — an integration platform that connects e-commerce stores, warehouses, marketplaces, ERPs, and POS systems, and keeps stock levels, orders, and products in sync across all of them.

This server lets AI agents (Claude, Cursor, or anything that speaks Model Context Protocol) build, run, and monitor those integrations end to end: connect two systems, preview the sync safely, and cut over to live — without a human clicking through a dashboard.

Why agents like it

generation, field-mapping suggestions); the sync engine itself is predictable, versioned, and observable.

• Deterministic runtime, no LLM in the hot path. AI helps at build time (connector

action:"preview" shows a structured source-vs-destination diff before anything is written.

• Safe by default. New flows start in shadow mode (read-only). pullpush.sync

(AES-256-GCM, per-tenant keys) server-side the moment they're created.

• Credentials never touch your machine or env. Connection secrets are envelope-encrypted

pullpush:// resources expose the tool catalog, quickstart, and agent guide — no pre-briefing needed.

• Self-describing. A get-started MCP prompt walks from zero to a working integration;

retryable} — an agent always knows the next step.

• Structured, actionable errors. Failures return {code, suggestion, suggestedTool,

dead-letter queue with retry, exponential backoff.

• Server-grade reliability. Circuit breakers, per-key ordered delivery, idempotency,

Try it in 60 seconds — no signup

curl -X POST https://api.pullpush.ai/api/sandbox

Returns a free 48-hour sandbox tenant: an API key, ready-to-paste MCP configs, and two pre-wired demo connections whose stock data deliberately disagrees — so your first pullpush.sync action:"preview" shows a real canonical diff (drifted quantities, a missing item, in-sync rows). The sandbox deletes itself on expiry — or keep it: POST /api/sandbox/claim (Bearer = the sandbox key, {"email": "..."}) converts it to a persistent free tenant with everything you built preserved.

Quick start

No clone or install needed — run directly via npx:

{
  "mcpServers": {
    "pullpush": {
      "command": "npx",
      "args": ["-y", "kaduno-pullpush-mcp@latest"],
      "env": {
        "PULLPUSH_API_KEY": "<your-api-key>"
      }
    }
  }
}

Add this to ~/.cursor/mcp.json (Cursor), Claude Desktop's config, or the MCP config for your client. Prefer a remote server? Connect straight to the hosted endpoint instead:

{
  "mcpServers": {
    "pullpush": {
      "type": "streamable-http",
      "url": "https://api.pullpush.ai/mcp",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Then ask your agent to run the get-started prompt — it walks through the whole flow: catalog connectors → create + test connections → suggest a field mapping → create the flow in shadow mode → preview the diff → cut over.

Getting an API key

For a throwaway key, use the sandbox above. For a persistent tenant:

1. Sign up free (1 connection, 1,000 events/month — no card)
2. Admin panel → Settings → API Keys
3. Create a key with the scope you need (tenant, org, or admin)

Tools

Shortened. The full README is on GitHub.