MULTI-APP TOOLKIT
Build with Blink + Samsung SmartThings
- Multi-app
- One MCP session
- 4 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Blink and Samsung SmartThings 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": "blink,smartthings",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Blink and Samsung SmartThings tools arrive
// together, each keyed by its own app's slug.
// e.g. run Get Feed Event:
const result = await mcp.callTool({
name: "blink-get-feed-event",
arguments: {
externalId: "External 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 [blinkTools, smartthingsTools] =
await Promise.all([
pd.components.list({ app: "blink" }),
pd.components.list({ app: "smartthings" }),
])
// 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=blink" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=smartthings" \
-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
Blink
Connected account
Samsung SmartThings
Connected account
TOOLS
Blink tools
The Blink tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Get Feed Event
actionGet a feed event by external ID. See the documentationRead-onlyv0.0.2 -
List Category ID Options
actionRetrieves available options for the Category ID field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1 -
Post feed
actionSend feed events to users. See the documentationWritev0.0.3
Triggers
No Blink triggers are available yet.
TOOLS
Samsung SmartThings tools
The Samsung SmartThings tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No Samsung SmartThings actions are available yet.
Triggers
No Samsung SmartThings 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
- blink,smartthings
- Primary app
- Blink (blink)
- Second app
- Samsung SmartThings (smartthings)
- Authentication
- API key + API key
- Available actions
- 4
- Available triggers
- 0