Model Context Protocol

Built for AI Agents

PullPush works natively with your AI assistant through the Model Context Protocol. Connect, map, preview, shadow, sync, monitor, and recover — all from your IDE.

The trust boundary: AI builds the integration. PullPush runs it deterministically. Every connector, mapping, transform, and workflow is versioned, previewable, testable, observable, and reversible.

MCP tools

Covering the full integration lifecycle

185

Integration actions

Across 18 domain routers

MCP resources

Tenant state, schemas, and runbooks

Guided prompts

Step-by-step agent workflows

Interactive widgets

Rich UI in your IDE chat

What agents can do

Create connector definitions

Generate working connectors from API docs, OpenAPI specs, Postman collections, or plain-language descriptions.

Modify existing connectors

Add endpoints, change authentication, update pagination logic, or extend support for custom fields.

Suggest field mappings

AI matches source fields to canonical schema and destination fields with confidence scores.

Add custom transform code

Write validation logic, data enrichment, conditional routing, or complex field transformations.

Compose multi-step workflows

Build DAGs that chain multiple connectors, transforms, filters, and conditional branches.

Run previews

Compare source and destination data side-by-side before any writes happen.

Inspect sync logs

Query event traces, view delivery status, and track data through the entire pipeline.

Investigate errors

Analyze dead-letter queue entries, identify root causes, and suggest the safest fix.

Retry failed events

Replay individual events or batches from the DLQ with one command.

Compare shadow-mode output

See exactly what would change if a connector went live — diff every record.

Roll back connector versions

Revert to any previous version of a connector definition safely and instantly.

Example prompts

These are real prompts you can give to any MCP-connected AI assistant (Claude, Cursor, GPT) with PullPush tools enabled.

"Build a connector for this supplier API from their OpenAPI file."

"Sync Magento customers to HubSpot contacts. Match by customer ID first, then email."

"Add support for this custom Magento customer attribute."

"Change the HubSpot mapping so customer group becomes lifecycle segment."

"Run this flow in shadow mode for 7 days and show me every difference."

"Create a workflow that sends failed orders to Slack after three retries."

"Add pagination and rate-limit handling to this connector."

"Inspect yesterday's failed events and suggest the safest fix."

48 MCP tools

Full integration lifecycle through MCP — connect, map, preview, shadow, sync, monitor, and recover. 185 integration actions across 18 domain routers.

Build

Generate and validate connectors from API documentation.

discovergenerate_connectorvalidate_definitiontest_connector

Connector Definitions

Manage the lifecycle of connector definitions.

list_definitionsget_definitioncreate_definitionupdate_definitionactivate_definitionpublish_definition

Canonical

Work with the canonical data model and field mappings.

list_canonical_typesvalidate_canonicalmap_fieldssuggest_mapping

Sync

Run previews, reconciliation, and inspect flow state.

preview_flowreconcile_flowflow_statusexplain_flow

Compose

Build and deploy multi-step workflow DAGs.

compose_workflowvalidate_workflowdeploy_workflow

Monitor

Monitor system health, inspect events, and manage the DLQ.

system_healthconnection_statusevent_statsdlq_listdlq_retry

Connect to your IDE

Copy-paste-ready configuration for Cursor, Claude Desktop, Windsurf, and other MCP clients. See the full guide for all clients and HTTP transport options.

Cursor

.cursor/mcp.json

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

Claude Desktop

claude_desktop_config.json

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

MCP documentation Full config snippets

The safety boundary

What AI does (build time)

✓ Read API documentation
✓ Generate connector definitions
✓ Suggest field mappings
✓ Write custom transform code
✓ Compose workflows
✓ Investigate errors and suggest fixes

What the runtime does (production)

✓ Execute versioned connector definitions
✓ Deliver events with per-key ordering
✓ Retry with exponential backoff
✓ Circuit-break on failures
✓ Deduplicate and guard against replays
✓ Encrypt all credentials per tenant

Start building integrations with AI

Connect PullPush to your AI assistant and start building connectors, mappings, and workflows in minutes.

Get API key →Read MCP docs