MULTI-APP TOOLKIT
Build with Brevo + Vercel
- Multi-app
- One MCP session
- 5 actions
- 7 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Brevo and Vercel tool at once — connect once, list tools, and call them like any single-app session.
// 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": "brevo,vercel_token_auth",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Brevo and Vercel tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add or Update a contact:
const result = await mcp.callTool({
name: "brevo-add-or-update-contact",
arguments: {
providedIdentifier: "Contact",
email: "Email",
},
})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 externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [brevoTools, vercelTokenAuthTools] =
await Promise.all([
pd.components.list({ app: "brevo" }),
pd.components.list({ app: "vercel_token_auth" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=brevo" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=vercel_token_auth" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
Brevo
Connected account
Vercel
Connected account
TOOLS
Brevo tools
The Brevo tools this pairing puts in reach, each one running on your user's own connected account.
Actions
TOOLS
Vercel tools
The Vercel tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Cancel Deployment
actionCancel a deployment which is currently building. See the documentationWritev0.0.6 -
Create Deployment
actionCreate a new deployment from a GitHub repository. See the documentationWritev0.0.6 -
List Deployments
actionList deployments under the account corresponding to the API token. See the documentationRead-onlyv0.0.6
Triggers top 4 of 5
-
Deployment Canceled (Instant)
triggerEmit new event when a deployment is canceled See the documentation.Instantv0.0.1 -
Deployment Error (Instant)
triggerEmit new event when a deployment encounters an error See the documentation.Instantv0.0.1 -
Deployment Succeeded (Instant)
triggerEmit new event when a deployment successfully completes See the documentation.Instantv0.0.1 -
New Deployment
triggerEmit new event when a deployment is createdv0.0.5
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- brevo,vercel_token_auth
- Primary app
- Brevo (brevo)
- Second app
- Vercel (vercel_token_auth)
- Authentication
- API key + API key
- Available actions
- 5
- Available triggers
- 7