Pipedream

Pipedream MCP Connector for Claude

A+

Manage Pipedream serverless workflows, sources, webhooks, and raw event data natively via AI agents.

7 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Pipedream automation workspace directly to any AI agent. Review the architecture of your serverless logic, audit event sources, and inspect real-time transaction limits or logic chains instantly without relying on the browser console.

What you can do

  • Workflows & Logic — List and drill down into serverless workflows, viewing configuration limits, step chains, and historical deployment statuses.
  • Event Sources — Retrieve detailed metadata for any configured Event Source, triggering webhooks, and polling configurations.
  • Real-Time Events — Intercept and summarize recent, raw physical payload transactions directly ingested by Pipedream endpoints.
  • Webhooks & Subscriptions — Map active system subscriptions connecting external APIs.

How it works

  1. Subscribe to this Pipedream server integration
  2. Provide your Pipedream API Key
  3. Start managing your automation logic directly from Claude, Cursor, or your preferred MCP client

Who is this for?

  • Integration Engineers — debug webhooks instantly, monitor workflow boundaries, and extract failing source logs directly into coding environments.
  • DevOps Teams — monitor webhook throughput or event ingest failures dynamically.
  • Automation Builders — map out complex step trees naturally via the agent without losing context of your broader systems.
serverlesswebhookapi-integrationevent-processingworkflow-orchestrationdata-pipelinedebugging

7 tools expose this connector's capabilities to your AI agent.

list_sources

List event sources

get_source

Get source details

list_workflows

List workflows

get_workflow

Get workflow details

list_events

List recent events from a source

list_subscriptions

List webhook subscriptions

get_user

Get current user info

See how to talk to your AI agent using Pipedream.

List the active event sources parsing my Slack webhooks.

You have 3 active HTTP Event Sources currently handling payloads. Source ID `src_xyz` (Slack Notifier) is polling normally, while `src_abc` (Stripe Charges) is temporarily paused due to rate limiting. Need to evaluate the recent transactions from Stripe?

Pull the raw events sent to the source `src_xyz982`.

I've pulled the 5 most recent events ingested by `src_xyz982`. The latest transaction executed 3 minutes ago captured a POST request with headers `{ 'content-type': 'application/json' }` and payload `{"user": "jane_doe", "action": "signup"}`. Wait, there's no email object attached. Should we review the workflow logic assigned to handle this?

Describe the node logic in workflow `wf_AByDk`.

Workflow `wf_AByDk` consists of 4 distinct steps: 1. `trigger_http` (Webhook inbound). 2. `format_data` (Custom code parsing Node.js strings). 3. `mysql_query` (Writes parameters to database). 4. `send_slack` (Dispatches confirmation notification). Everything appears fully active with zero deployment errors recorded. Would you like the explicit code logic in the `format_data` block?

Yes. Ask the agent to list recent events from a specific Event Source ID. It captures the physical payloads ingested, showing you the raw keys and headers automatically. This is perfect for debugging failed external API calls without leaving your environment.

Related Connectors