Can I use Pipedream as a CLI?

Yes. KosmoKrator exposes a Pipedream CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pipedream through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pipedream tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pipedream credentials stored?

Pipedream credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pipedream MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

automation

Pipedream MCP Integration for Generic MCP Clients

Connect Pipedream to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Pipedream feedback View package source

Connect Pipedream to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Pipedream MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-pipedream": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=pipedream",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=pipedream --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Pipedream instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Pipedream Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Pipedream integration catalog.

MCP tool	Source function	Type	Description
`integration__pipedream__pipedream_list_workflows`	`pipedream.pipedream_list_workflows`	Read	List automation workflows in Pipedream. Returns a paginated list of workflows with their IDs, names, and statuses.
`integration__pipedream__pipedream_get_workflow`	`pipedream.pipedream_get_workflow`	Read	Get details of a specific Pipedream workflow by ID, including its configuration, steps, and current status.
`integration__pipedream__pipedream_list_components`	`pipedream.pipedream_list_components`	Read	List available Pipedream components (actions, triggers, etc.). Components are reusable building blocks for connecting to third-party APIs.
`integration__pipedream__pipedream_get_component`	`pipedream.pipedream_get_component`	Read	Get details of a specific Pipedream component by app and component key. Returns the component configuration, props, and version info.
`integration__pipedream__pipedream_list_connected_accounts`	`pipedream.pipedream_list_connected_accounts`	Read	List connected third-party accounts in Pipedream. These are the OAuth-connected accounts used by workflows to interact with external services.
`integration__pipedream__pipedream_list_triggers`	`pipedream.pipedream_list_triggers`	Read	List event triggers for a specific Pipedream workflow. Triggers define the events that cause a workflow to run.
`integration__pipedream__pipedream_get_current_user`	`pipedream.pipedream_get_current_user`	Read	Get the currently authenticated Pipedream user profile, including name, email, and workspace details.

Related Pipedream Pages

Pipedream CLIUse direct JSON commands instead of MCP discovery. Pipedream MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.