MULTI-APP TOOLKIT
Build with Brevo + Keycloak
- Multi-app
- One MCP session
- 7 actions
- 3 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Brevo and Keycloak 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,keycloak",
},
},
},
)
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 Keycloak 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, keycloakTools] =
await Promise.all([
pd.components.list({ app: "brevo" }),
pd.components.list({ app: "keycloak" }),
])
// 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=keycloak" \
-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
Keycloak
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
Keycloak tools
The Keycloak tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create User
actionCreate a new user in Keycloak. The username must be unique. See the documentationWritev0.0.2 -
Delete User
actionDelete a user from Keycloak. See the documentationWritev0.0.2 -
Get User
actionRetrieve the representation of the user. See the documentationRead-onlyv0.0.2 -
List Realm Options
actionRetrieves available options for the Realm field.Read-onlyv0.0.1 -
Update User
actionUpdates a user in Keycloak. See the documentationWritev0.0.2
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,keycloak
- Primary app
- Brevo (brevo)
- Second app
- Keycloak (keycloak)
- Authentication
- API key + OAuth
- Available actions
- 7
- Available triggers
- 3