MULTI-APP TOOLKIT
Build with Home Assistant + Opsgenie
- Multi-app
- One MCP session
- 6 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Home Assistant and Opsgenie 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": "home_assistant,opsgenie",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Home Assistant and Opsgenie tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Note to Alert:
const result = await mcp.callTool({
name: "opsgenie-add-note-alert",
arguments: {
alertId: "Alert ID",
note: "Note",
},
})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 [homeAssistantTools, opsgenieTools] =
await Promise.all([
pd.components.list({ app: "home_assistant" }),
pd.components.list({ app: "opsgenie" }),
])
// 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=home_assistant" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=opsgenie" \
-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
Home Assistant
Connected account
Opsgenie
Connected account
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.
TOOLS
Opsgenie tools
The Opsgenie tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Add Note to Alert
actionAdds a note to an existing alert in Opsgenie. See the documentationWritev0.0.2 -
Create Alert
actionSend a new Alert for processing. See the documentationWritev0.0.3 -
Delete Alert
actionRemoves an existing alert from Opsgenie. See the documentationWritev0.0.2 -
Get Alert Status
actionGet the status of the alert with the specified ID. See the documentationRead-onlyv0.0.3 -
List Alert ID Options
actionRetrieves available options for the Alert ID field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1
Triggers
No Opsgenie 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
- home_assistant,opsgenie
- Primary app
- Home Assistant (home_assistant)
- Second app
- Opsgenie (opsgenie)
- Authentication
- API key + API key
- Available actions
- 6
- Available triggers
- 0