MULTI-APP TOOLKIT
Build with IMAP + Playwright
- Multi-app
- One MCP session
- 5 actions
- 1 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every IMAP and Playwright 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": "imap,playwright",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: IMAP and Playwright tools arrive
// together, each keyed by its own app's slug.
// e.g. run List Mailbox Options:
const result = await mcp.callTool({
name: "imap-list-mailbox-options",
arguments: {},
})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 [imapTools, playwrightTools] =
await Promise.all([
pd.components.list({ app: "imap" }),
pd.components.list({ app: "playwright" }),
])
// 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=imap" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=playwright" \
-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
IMAP
Connected account
Playwright
Connected account
TOOLS
IMAP tools
The IMAP tools this pairing puts in reach, each one running on your user's own connected account.
TOOLS
Playwright tools
The Playwright tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Get Page HTML
actionReturns the page's html. See the documentationRead-onlyv0.0.4 -
Get Page Title
actionReturns the page's title. See the documentationRead-onlyv0.0.4 -
Page PDF
actionGenerates a pdf of the page and store it on /tmp directory. See the documentationWritev0.0.5 -
Take Screenshot
actionStore a new screenshot file on /tmp directory. See the documentationWritev0.0.5
Triggers
No Playwright 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
- imap,playwright
- Primary app
- IMAP (imap)
- Second app
- Playwright (playwright)
- Authentication
- API key + API key
- Available actions
- 5
- Available triggers
- 1