MULTI-APP TOOLKIT
Build with Hamsa + LiveKit
- Multi-app
- One MCP session
- 12 actions
- 1 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Hamsa and LiveKit 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": "hamsa,livekit",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Hamsa and LiveKit tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create AI Content:
const result = await mcp.callTool({
name: "hamsa-create-content",
arguments: {
jobId: "Job Id",
aiParts: ["AI Parts"],
},
})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 [hamsaTools, livekitTools] =
await Promise.all([
pd.components.list({ app: "hamsa" }),
pd.components.list({ app: "livekit" }),
])
// 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=hamsa" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=livekit" \
-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
Hamsa
Connected account
LiveKit
Connected account
TOOLS
Hamsa tools
The Hamsa tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create AI Content
actionTransform transcribed content into various formats for content marketing. See the documentationWritev0.0.2 -
List Job Id Options
actionRetrieves available options for the Job Id field.Read-onlyv0.0.1 -
List Jobs
actionFetch the list of jobs from Hamsa. See the documentationRead-onlyv0.0.2 -
List Voice ID Options
actionRetrieves available options for the Voice ID field.Read-onlyv0.0.1 -
Synthesize Voice
actionConverts text input into artificial speech using Hamsa. See the documentationRead-onlyv0.0.2 -
Transcribe Video
actionAutomatically transcribe Arabic videos from YouTube URLs or direct links. See the documentationWritev0.0.2
Triggers
No Hamsa triggers are available yet.
TOOLS
LiveKit tools
The LiveKit tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Ingress From URL
actionCreate a new ingress from url in LiveKit. See the documentation.Writev0.0.3 -
Create Room
actionCreate a new room in LiveKit. See the documentation.Writev0.0.3 -
Delete Room
actionDelete a room in LiveKit. See the documentationWritev0.0.3 -
Generate Access Token
actionGenerate an access token for a participant to join a LiveKit room. See the documentation.Writev0.0.2 -
List Rooms
actionList all rooms with LiveKit. See the documentation.Read-onlyv0.0.3 -
Remove Participants
actionRemove specific participants from a LiveKit room. See the documentation.Writev0.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
- hamsa,livekit
- Primary app
- Hamsa (hamsa)
- Second app
- LiveKit (livekit)
- Authentication
- API key + API key
- Available actions
- 12
- Available triggers
- 1