MULTI-APP TOOLKIT
Build with Blizzard Battle.net + Home Assistant
- Multi-app
- One MCP session
- 0 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Blizzard Battle.net and Home Assistant 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": "battle_net,home_assistant",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Blizzard Battle.net and Home Assistant tools arrive
// together, each keyed by its own app's slug.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 [battleNetTools, homeAssistantTools] =
await Promise.all([
pd.components.list({ app: "battle_net" }),
pd.components.list({ app: "home_assistant" }),
])
// 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=battle_net" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=home_assistant" \
-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
Blizzard Battle.net
Connected account
Home Assistant
Connected account
TOOLS
Blizzard Battle.net tools
The Blizzard Battle.net tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No Blizzard Battle.net actions are available yet.
Triggers
No Blizzard Battle.net triggers are available yet.
TOOLS
Home Assistant tools
The Home Assistant tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No Home Assistant actions are available yet.
Triggers
No Home Assistant 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
- battle_net,home_assistant
- Primary app
- Blizzard Battle.net (battle_net)
- Second app
- Home Assistant (home_assistant)
- Authentication
- OAuth + API key
- Available actions
- 0
- Available triggers
- 0