Reply icon

CONNECT APP

Build with Reply

Digital Services, Technology and Consulting

Marketing

  • API key

MCP

Give your agent Reply tools

Every Reply action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Reply account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "reply",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()
// Every tool arrives with its own input schema — run one with mcp.callTool().

API PROXY

Call the Reply API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Reply API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.reply.io/v1/people",
})

// Any allowed Reply endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Reply actions from your backend

Connect a user's Reply account once, then discover and run its tools on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const tools = await pd.components.list({
  app: "reply",
  componentType: "action",
})

TOOLS

Reply actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

No Reply actions are available yet.

EVENTS

Reply triggers

Event sources your backend can deploy for users and receive through a webhook.

No Reply triggers are available yet.

MULTI-APP

Use Reply with other popular apps

Most products don't stop at one integration. Pair Reply with the other apps your users rely on, and ship use cases that span both.

REFERENCE

App details

Reference metadata for the Reply connector in the Pipedream registry.

App slug
reply
Authentication
API key
Categories
Marketing
Actions
0
Triggers
0
API proxy
Available