Dbx vs Pullpush MCP
A side-by-side look at the Dbx and Pullpush MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dbx for databases work as a local process; choose Pullpush MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dbx when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Pullpush MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pullpush.connection.create, pullpush.connection.test, pullpush.connection.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 56/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 27,663 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 45 |
| Full listing | View Dbx | View Pullpush MCP |
Tools & capabilities
Dbx tools
No tool names declared yet. Check the project README from the listing page.
Pullpush MCP tools 45
pullpush.connection.createCreate and configure a connection to an external system (Shopify, WooCommerce, Linnworks, Xero, HubSpot, and 20+ more)pullpush.connection.testTest live connection credentials; returns health metrics and failure countpullpush.connectionList, get, update, delete, and configure connections (router with actions: list, get, update, delete, health, config)pullpush.flow.createWire a source→destination sync pipeline with triggers, mapping, and canonical data modelspullpush.flow.dryRunDry-run an event through flow transform/filter without delivery; returns mapped payloadpullpush.flow.naturalCreate a flow from a natural-language description; proposes mapping and creates in shadow modepullpush.flowList, get, update, pause/resume, delete flows and view delivery history (router)pullpush.sync.reconcileReconcile-and-deliver: diff source vs destination, then deliver changes with per-item progresspullpush.syncPreview 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)pullpush.mapping.suggestAI-proposes field mapping from source sample to target shape; returns mapping, confidence, previewpullpush.mapping.validateValidate a mapping config against source and destination schemaspullpush.mapping.compareCompare two mappings side by side- +33 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dbx
{
"mcpServers": {
"dbx": {
"command": "npx",
"args": [
"-y",
"@dbx-app/mcp-server"
]
}
}
}
Pullpush MCP
{
"mcpServers": {
"pullpush-mcp": {
"command": "npx",
"args": [
"-y",
"kaduno-pullpush-mcp"
]
}
}
}
Frequently asked questions
Dbx is categorized under Databases and uses a local stdio subprocess. Pullpush MCP belongs to Databases and uses a local stdio subprocess. Pick Dbx for databases work and Pullpush MCP for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dbx is listed as free. Auth: no auth required. Pullpush MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dbx and pullpush-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dbx has a quality signal of 56/100 (Good) with 6 views, 0 installs and 27,663 GitHub stars. Pullpush MCP has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.