Pullpush MCP

Name: Pullpush MCP
Author: Kaduno-systems

by Kaduno-systemsversion 2.4.0i★ –iComputer or cloud

Registry nameai.pullpush/pullpush-mcp

Install

Overview

Description from the maker (original English)

Connect any two APIs and keep them in sync — 50 MCP tools with shadow previews and diagnostics.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: PULLPUSH_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: PULLPUSH_API_KEY, PULLPUSH_API_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.pullpush.ai/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "pullpush": {
      "command": "npx",
      "args": [
        "-y",
        "kaduno-pullpush-mcp"
      ],
      "env": {
        "PULLPUSH_API_KEY": "your-value",
        "PULLPUSH_API_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http pullpush https://api.pullpush.ai/mcp

Or run it on your computer

claude mcp add pullpush --env PULLPUSH_API_KEY=your-value --env PULLPUSH_API_URL=your-value -- npx -y kaduno-pullpush-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pullpush": {
      "url": "https://api.pullpush.ai/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pullpush": {
      "command": "npx",
      "args": [
        "-y",
        "kaduno-pullpush-mcp"
      ],
      "env": {
        "PULLPUSH_API_KEY": "your-value",
        "PULLPUSH_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pullpush": {
      "type": "http",
      "url": "https://api.pullpush.ai/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pullpush": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "kaduno-pullpush-mcp"
      ],
      "env": {
        "PULLPUSH_API_KEY": "your-value",
        "PULLPUSH_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.pullpush.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

PULLPUSH_API_KEY secret required env
Your PullPush API key (admin panel → Settings → API Keys).
PULLPUSH_API_URL env
API base URL. Override only for self-hosted instances.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pullpush.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32398 servers in this category
Published to the registry more recently than 85% of the other 32398 servers in this category
Basic checks equal to or better than 100% of the other 32398 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pullpush MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PULLPUSH_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.4.0) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

AI Deprecations

by aideprecations.com

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Deterministic runtime, no LLM in the hot path. AI helps at build time (connector generation, field-mapping suggestions); the sync engine itself is predictable, versioned, and observable.
Safe by default. New flows start in shadow mode (read-only). pullpush.sync action:"preview" shows a structured source-vs-destination diff before anything is written.
Credentials never touch your machine or env. Connection secrets are envelope-encrypted (AES-256-GCM, per-tenant keys) server-side the moment they're created.
Self-describing. A get-started MCP prompt walks from zero to a working integration; pullpush:// resources expose the tool catalog, quickstart, and agent guide — no pre-briefing needed.
Structured, actionable errors. Failures return {code, suggestion, suggestedTool, retryable} — an agent always knows the next step.
Server-grade reliability. Circuit breakers, per-key ordered delivery, idempotency, dead-letter queue with retry, exponential backoff.

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

Connect straight to the hosted endpoint. It is the most robust option — nothing runs on your machine, so there is no process to crash or go stale:

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

Add this to ~/.cursor/mcp.json (Cursor), Claude Desktop's config, or the MCP config for your client.

Clients that only speak stdio

Use this package as a local stdio proxy to the same endpoint. Install a pinned version once and run the binary — do not use npx ...@latest, which re-resolves the package (and needs the network) every time your client starts the server:

npm i -g kaduno-pullpush-mcp@2.4.0

"mcpServers": { "pullpush": { "command": "kaduno-pullpush-mcp", "env": { "PULLPUSH_API_KEY": " " } } } }

The proxy never exits because the API is unreachable: it starts, answers your client, and connects in the background (exponential backoff, honouring Retry-After). It reconnects after a network blip or an API restart, and while it is offline a tool call returns a retryable "reconnecting" error that changes nothing. The tool catalogue is cached on disk, so a restart while the API is down still lists your tools.

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:

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

Tools

50 tools (30 explicit tools plus 228 actions across 20 domain routers) covering the full integration lifecycle. Explicit tools are individually named; domain routers accept an action parameter with multiple operations.

Connections

pullpush.connection.create — Create and configure a connection to an external system (Shopify, WooCommerce, Linnworks, Xero, HubSpot, and 20+ more)
pullpush.connection.test — Test live connection credentials; returns health metrics and failure count
pullpush.connection — List, get, update, delete, and configure connections (router with actions: list, get, update, delete, health, config)

Flows

pullpush.flow.create — Wire a source→destination sync pipeline with triggers, mapping, and canonical data models
pullpush.flow.dryRun — Dry-run an event through flow transform/filter without delivery; returns mapped payload
pullpush.flow.natural — Create a flow from a natural-language description; proposes mapping and creates in shadow mode
pullpush.flow — List, get, update, pause/resume, delete flows and view delivery history (router)

Sync & reconciliation

pullpush.sync.reconcile — Reconcile-and-deliver: diff source vs destination, then deliver changes with per-item progress
pullpush.sync — Preview diffs, snapshot data, inspect single keys, scan catalogs, diagnose unmatched SKUs, manage baselines (router with actions: preview, snapshot, inspect, reconcile, scan, reset-baseline, baseline.history, baseline.rollback, channel-cache, unmatched)

Field mapping

pullpush.mapping.suggest — AI-proposes field mapping from source sample to target shape; returns mapping, confidence, preview
pullpush.mapping.validate — Validate a mapping config against source and destination schemas
pullpush.mapping.compare — Compare two mappings side by side
pullpush.mapping.explain — Explain how a mapping transforms data, step by step
pullpush.mapping.diff — Diff two mapping versions to see what changed
pullpush.mapping.get — Get a flow's current mapping config, source fields, and destination fields

Diagnostics

pullpush.explain — Diagnose why a flow, connection, or delivery failed; gathers errors, identifies patterns, suggests fixes
pullpush.diagnose.recent — Scan all flows for recent failures; returns a prioritized issue list
pullpush.ask — Answer natural-language ops questions using tenant failures and anomalies

Connector authoring

pullpush.connector.generate — AI-generates TypeScript connector code, typechecks, tests, and registers
pullpush.connector — List, get, update, and manage connector definitions (router)

Data operations

pullpush.data.push — Push file data (CSV, JSON, XML) into a connection
pullpush.import — File-based data import operations (router)
pullpush.export — Scheduled export pipelines: create, list, update, delete, test, run (router)
pullpush.canonical — Inspect and manage canonical data models (router)

Shadow mode & safety

pullpush.shadow — Run integrations read-only before going live; compare shadow vs live results (router)

Batch operations

pullpush.batch.test — Test multiple connections in parallel
pullpush.batch.status — Get status matrix across all flows
pullpush.batch.setup — One-call setup: create connections + flow + test in one operation
pullpush.batch — Multi-flow batch operations and proactive reports (router)

Ops & health

pullpush.health.overview — Tenant health dashboard: connections, flows, failures, backlog, delivery rate, anomalies
pullpush.health.mcp — MCP server health: database, tools registered, uptime
pullpush.ops — Anomaly detection, dead-letter recovery, operation monitoring (router)

Workflows

pullpush.workflow.create — Create multi-step workflow with trigger and step DAG
pullpush.workflow.trigger — Manually trigger a workflow run from an existing event
pullpush.workflow — List, get, and manage workflows (router)

Integrations & marketplace

pullpush.integration.create — Create an integration grouping flows/workflows under one name
pullpush.integration — List and manage integrations (router)
pullpush.marketplace.install — Install a marketplace listing into your tenant
pullpush.marketplace — Browse and manage marketplace connectors (router)
pullpush.destination.provision — Provision custom fields on destination API (e.g. HubSpot properties)

Administration

pullpush.tenant — Tenant management: list, get, create, update (router)
pullpush.billing — Subscription and usage management (router)
pullpush.partner — Partner program operations (router)
pullpush.backup — Backup and restore operations (router)
pullpush.feedback — Submit feedback about MCP tool quality or missing features

Full tool reference: pullpush.ai/docs/mcp

Environment variables

Variable	Required	Default	Description
`PULLPUSH_API_KEY`	Yes	—	Your PullPush API key
`PULLPUSH_API_URL`	No	`https://api.pullpush.ai`	API base URL (override for self-hosted)
`PULLPUSH_CACHE_DIR`	No	OS cache directory	Where the tool catalogue is cached
`PULLPUSH_TIMEOUT_MS`	No	`55000`	How long a tool call may take before the proxy answers with a timeout error

Auth scopes

Scope	Access
Tenant key	Your tenant's connections, flows, sync, diagnostics
Org key	All tenants in your organization (read or read+write)
Admin key	Full platform access (billing, partners, all tenants)

Tools are automatically scoped: a tenant key never sees another tenant's data.

Features

Never dies on a bad connection: starts even when the API is down, reconnects on its own, and serves a cached tool catalogue meanwhile
Auto-refresh: tool catalog refreshes every 5 minutes — new server-side tools appear without a restart (clients are notified only when the catalogue really changed)
Offline quickstart: built-in pullpush://docs/quickstart-local resource works without network
Retry on unknown tool: automatically refreshes the catalog when a tool is not found
Clear error messages: auth failures, network issues, and version mismatches are explained

Documentation

Getting started — 5 minutes to a first integration
MCP guide — full tool reference and client setup
Shadow mode · Preview & reconcile · Security
llms.txt — machine-readable product summary
Machine-readable integration catalog
MCP registry entry: ai.pullpush/pullpush-mcp

Also available: pullpush-mcp-dev

For connector authors, platform admins, and internal developers, pullpush-mcp-dev exposes additional tools for:

AI-powered connector generation and composition
Canonical schema management
Marketplace publishing
Billing and partner administration
Batch operations across all tenants

Development

git clone https://github.com/Kaduno-systems/pullpush-mcp.git

Only the beginning is shown; read the rest in the repo

Pullpush MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

AI Deprecations

README from the maker

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

Why agents like it

Try it in 60 seconds — no signup

Quick start

Clients that only speak stdio

Getting an API key

Tools

Connections

Flows

Sync & reconciliation

Field mapping

Diagnostics

Connector authoring

Data operations

Shadow mode & safety

Batch operations

Ops & health

Workflows

Integrations & marketplace

Administration

Environment variables

Auth scopes

Features

Documentation

Also available: pullpush-mcp-dev

Development