View as Markdown
KnowBe4 icon Splunk HTTP Event Collector icon

MULTI-APP TOOLKIT

Build with KnowBe4 + Splunk HTTP Event Collector

Connect a user's KnowBe4 and Splunk HTTP Event Collector accounts and expose tools for both apps directly in your product or your agent.
  • Multi-app
  • One MCP session
  • 3 actions
  • 0 triggers
  • Managed auth

MCP

One MCP session, both toolsets

One session gives your product or agent every KnowBe4 and Splunk HTTP Event Collector 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": "knowbe4,splunk_http_event_collector",
      },
    },
  },
)

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

const { tools } = await mcp.listTools()

// One list, both toolsets: KnowBe4 and Splunk HTTP Event Collector tools arrive
// together, each keyed by its own app's slug.

// e.g. run Check Splunk HTTP Event Collector Health:
const result = await mcp.callTool({
  name: "splunk_http_event_collector-check-health",
  arguments: {},
})

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

KnowBe4

Connected account

Splunk HTTP Event Collector

Connected account

TOOLS

KnowBe4 tools

The KnowBe4 tools this pairing puts in reach, each one running on your user's own connected account.

View all 0 KnowBe4 tools →

Actions

No KnowBe4 actions are available yet.

Triggers

No KnowBe4 triggers are available yet.

x-pd-app-slug
knowbe4,splunk_http_event_collector
Primary app
KnowBe4 (knowbe4)
Second app
Splunk HTTP Event Collector (splunk_http_event_collector)
Authentication
API key + API key
Available actions
3
Available triggers
0