MULTI-APP TOOLKIT
Build with Drata + NinjaOne
- Multi-app
- One MCP session
- 21 actions
- 9 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Drata and NinjaOne 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": "drata,ninjaone",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Drata and NinjaOne tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Asset:
const result = await mcp.callTool({
name: "drata-create-asset",
arguments: {
name: "Name",
description: "Description",
},
})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 [drataTools, ninjaoneTools] =
await Promise.all([
pd.components.list({ app: "drata" }),
pd.components.list({ app: "ninjaone" }),
])
// 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=drata" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=ninjaone" \
-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
Drata
Connected account
NinjaOne
Connected account
TOOLS
Drata tools
The Drata tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 14
-
Create Asset
actionCreate an asset. See the documentation.Writev0.0.4 -
Create Control
actionCreate a new Control. See the documentation.Writev0.0.4 -
Create Vendor
actionCreate a new Vendor. See the documentation.Writev0.0.4 -
Find Controls
actionFind Controls. See the documentation.Read-onlyv0.0.4 -
Find Personnel
actionFind Personnel. See the documentation.Read-onlyv0.0.4 -
Find Vendors
actionFind Vendors. See the documentation.Read-onlyv0.0.4 -
List Control ID Options
actionRetrieves available options for the Control ID field.Read-onlyv0.0.1 -
List Device ID Options
actionRetrieves available options for the Device ID field.Read-onlyv0.0.1
Triggers top 4 of 8
-
Employee Terminated
triggerEmit a new event when an employee is terminated. See the documentation.v0.0.3 -
Failed Monitor
triggerEmit a new event whenever a monitor fails. See the documentation.v0.0.2 -
New Asset Added
triggerEmit a new event for every new asset. See the documentation.v0.0.3 -
New Control Added
triggerEmit a new event for every new control. See the documentation.v0.0.3
TOOLS
NinjaOne tools
The NinjaOne tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Support Ticket
actionCreates a new support ticket in NinjaOne. See the documentationWritev0.0.2 -
List Assigned App User ID Options
actionRetrieves available options for the Assigned App User ID field.Read-onlyv0.0.1 -
List Node Role Id Options
actionRetrieves available options for the Node Role Id field.Read-onlyv0.0.1 -
List Policy ID Options
actionRetrieves available options for the Policy ID field.Read-onlyv0.0.1 -
List Status Options
actionRetrieves available options for the Status field.Read-onlyv0.0.1 -
List Ticket Form ID Options
actionRetrieves available options for the Ticket Form ID field.Read-onlyv0.0.1 -
Update Device
actionUpdate details for a specific device in NinjaOne. See the documentationWritev0.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
- drata,ninjaone
- Primary app
- Drata (drata)
- Second app
- NinjaOne (ninjaone)
- Authentication
- API key + OAuth
- Available actions
- 21
- Available triggers
- 9