MULTI-APP TOOLKIT

Build with Directus + Google Maps (Places API)

Connect a user's Directus and Google Maps (Places API) accounts and expose tools for both apps directly in your product or your agent.

Multi-app
One MCP session
2 actions
0 triggers
Managed auth

Start building

MCP

One MCP session, both toolsets

One session gives your product or agent every Directus and Google Maps (Places API) tool at once — connect once, list tools, and call them like any single-app session.

Pipedream Connect

// 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": "directus,google_maps_platform",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// One list, both toolsets: Directus and Google Maps (Places API) tools arrive
// together, each keyed by its own app's slug.

// e.g. run Get Place Details:
const result = await mcp.callTool({
  name: "google_maps_platform-get-place-details",
  arguments: {
    placeId: "Place ID",
    simplified: true,
  },
})

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 [directusTools, googleMapsPlatformTools] =
  await Promise.all([
    pd.components.list({ app: "directus" }),
    pd.components.list({ app: "google_maps_platform" }),
  ])

// 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=directus" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}"

curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=google_maps_platform" \
  -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.

MCP guide →

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

Directus

Connected account

Google Maps (Places API)

Connected account

TOOLS