Connect any two APIs and keep them in sync — 45 MCP tools with shadow previews and diagnostics.
Connect any two APIs and keep them in sync — 45 MCP tools with shadow previews and diagnostics. Exposed over MCP by the pullpush mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
Connections — The Connections tool exposed by this serverFlows — The Flows tool exposed by this serverDiagnostics — The Diagnostics tool exposed by this serverWorkflows — The Workflows tool exposed by this serverAdministration — Full tool reference: pullpush.ai/docs/mcpBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: PULLPUSH_API_KEY, PULLPUSH_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Pullpush's toolset — Connections, Flows, Diagnostics and 2 more — is a fair guide to whether it matches your workflow. It is maintained by ai.pullpush; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Connections | The Connections tool exposed by this server. |
| Flows | The Flows tool exposed by this server. |
| Diagnostics | The Diagnostics tool exposed by this server. |
| Workflows | The Workflows tool exposed by this server. |
| Administration | Full tool reference: [pullpush.ai/docs/mcp](https://pullpush.ai/docs/mcp) |
{
"mcpServers": {
"pullpush": {
"command": "npx",
"args": ["-y", "npm"],
"env": {
"PULLPUSH_API_KEY": "your-value",
"PULLPUSH_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PULLPUSH_API_KEY | Credential the server authenticates with. | Yes |
| PULLPUSH_API_URL | Endpoint or connection string the server talks to. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.