MULTI-APP TOOLKIT
Build with Figma + Metabase
- Multi-app
- One MCP session
- 10 actions
- 1 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Figma and Metabase 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": "figma,metabase",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Figma and Metabase tools arrive
// together, each keyed by its own app's slug.
// e.g. run Delete a Comment:
const result = await mcp.callTool({
name: "figma-delete-comment",
arguments: {
projectId: "Project Id",
fileId: "File Id",
},
})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 [figmaTools, metabaseTools] =
await Promise.all([
pd.components.list({ app: "figma" }),
pd.components.list({ app: "metabase" }),
])
// 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=figma" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=metabase" \
-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
Figma
Connected account
Metabase
Connected account
TOOLS
Figma tools
The Figma tools this pairing puts in reach, each one running on your user's own connected account.
Actions
TOOLS
Metabase tools
The Metabase tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Dashboard
actionCreate a new Dashboard. See the documentation.Writev0.0.4 -
Export Query with Format
actionExecute a saved question/card with parameters and export results in the specified format (CSV, JSON, XLSX, or API). See the documentation.Read-onlyv0.0.1 -
Get Dashboard
actionRetrieve dashboard information and its cards. See the documentation.Read-onlyv0.0.4 -
Get Database
actionRetrieve database information. See the documentation.Read-onlyv0.0.4 -
List Card ID Options
actionRetrieves available options for the Card ID field.Read-onlyv0.0.1 -
List Collection ID Options
actionRetrieves available options for the Collection ID field.Read-onlyv0.0.1 -
Run Query
actionExecute a saved question/card and return the results. See the documentation.Writev0.0.4
Triggers
No Metabase triggers are available yet.
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
- figma,metabase
- Primary app
- Figma (figma)
- Second app
- Metabase (metabase)
- Authentication
- OAuth + API key
- Available actions
- 10
- Available triggers
- 1