MULTI-APP TOOLKIT
Build with Elastic Cloud + Playwright
- Multi-app
- One MCP session
- 12 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Elastic Cloud 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": "elastic_cloud,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: Elastic Cloud and Playwright tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Deployment:
const result = await mcp.callTool({
name: "elastic_cloud-create-deployment",
arguments: {
name: "Name",
region: "Region",
},
})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 [elasticCloudTools, playwrightTools] =
await Promise.all([
pd.components.list({ app: "elastic_cloud" }),
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=elastic_cloud" \
-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
Elastic Cloud
Connected account
Playwright
Connected account
TOOLS
Elastic Cloud tools
The Elastic Cloud tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Deployment
actionCreate a new Elastic Cloud deployment. Requires a name, region, and version at minimum. Provide theresourcesJSON object to configure Elasticsearch/Kibana/APM topology; omit it to accept region defaults. See the documentationWritev0.0.2 -
Create Traffic Filter Ruleset
actionCreate a new traffic filter ruleset in Elastic Cloud. The API requires a name, type, region, rules, and include-by-default flag. Note thattypeandregioncannot be changed after the ruleset is created. See the documentationWritev0.0.2 -
Delete Traffic Filter Ruleset
actionPermanently delete a traffic filter ruleset from Elastic Cloud. This is irreversible. Run List Traffic Filter Rulesets first to find the ruleset ID. See the documentationWritev0.0.2 -
Get Deployment
actionRetrieve a single Elastic Cloud deployment by ID. Run List Deployments first to find a valid deployment ID. See the documentationRead-onlyv0.0.2 -
List Deployments
actionList all deployments in your Elastic Cloud organization. Use this first to discover deployment IDs before calling Get Deployment or Update Deployment. See the documentationRead-onlyv0.0.2 -
List Traffic Filter Rulesets
actionList all traffic filter rulesets in your Elastic Cloud organization. Use this first to discover ruleset IDs before calling Update Traffic Filter Ruleset or Delete Traffic Filter Ruleset. See the documentationRead-onlyv0.0.2 -
Update Deployment
actionUpdate an existing Elastic Cloud deployment, including resizing cluster capacity. Cluster resize is performed here by supplying updatedresourcessizing (no separate resize action exists). Run List Deployments first to find the deployment ID. See the documentationWritev0.0.2 -
Update Traffic Filter Ruleset
actionUpdate an existing traffic filter ruleset in Elastic Cloud. The underlying API replaces the whole ruleset, so this action first reads the current ruleset and merges your changes over it — supply only the fields you want to change. The ruleset'stypeandregionare immutable after creation and are carried over automatically. Run List Traffic Filter Rulesets first to find the ruleset ID. See the documentationWritev0.0.2
Triggers
No Elastic Cloud triggers are available yet.
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
- elastic_cloud,playwright
- Primary app
- Elastic Cloud (elastic_cloud)
- Second app
- Playwright (playwright)
- Authentication
- API key + API key
- Available actions
- 12
- Available triggers
- 0