# Prisma Cloud MCP connector

Connecting Prisma Cloud to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up cloud accounts, access keys, adoption reports and vulnerability trends, each person inside their own access, every call logged.

Source: https://elaichi.ai/connectors/prismacloud/

## Facts

| | |
| --- | --- |
| Application | Prisma Cloud |
| Category | Security |
| AI tools | 629 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Prisma Cloud is connected

- Which Prisma Cloud access keys are still active for the platform team?
- Show the compute vulnerability trend over the last month
- List cloud accounts whose status is not healthy right now

## Connect Prisma Cloud in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Prisma Cloud.
2. Optionally set Share with, then press Connect.
3. Paste a Prisma Cloud API key. One person generates a token in Prisma Cloud and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Prisma Cloud tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Prisma Cloud MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Prisma Cloud MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Prisma Cloud MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Prisma Cloud MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Prisma Cloud MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Prisma Cloud to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Prisma Cloud tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Prisma Cloud through Elaichi

### Audit access keys before the quarterly review

Security. Ask for every Prisma Cloud access key, who it belongs to and whether it is still active, then disable the stale ones in one pass instead of clicking through them individually.

### Find cloud accounts that are not healthy

Cloud operations. Check the onboarding and configuration status of every connected cloud account and AWS organization, and get a short list of the ones that need attention this morning.

### Pull the adoption report without logging in

Compliance. Ask for the latest Prisma Cloud adoption report and its checks, and have it summarized for the steering meeting without opening the console.

### Track compute vulnerabilities week over week

Platform engineering. Ask how the vulnerability trend across compute workloads has moved since last week and which direction the secured versus discovered numbers are heading.

### Watch the risky asset trend

Risk. Get the risky asset trend from Prisma Cloud posture data in plain language, so the monthly risk update takes minutes rather than an afternoon.

### Retire access keys when a project ends

IT. When a contractor rolls off, ask for the Prisma Cloud access keys tied to them and have them disabled or deleted, with the change recorded against your name.

## Elaichi vs Zapier MCP vs Composio for Prisma Cloud

All three can connect Prisma Cloud to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Prisma Cloud tools | Allow or restrict single Prisma Cloud tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Prisma Cloud call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Prisma Cloud to Claude?

Connect Prisma Cloud in Elaichi by pasting a Prisma Cloud API key, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Prisma Cloud accounts, access keys and reports are available in your next conversation.

### Does Prisma Cloud work with ChatGPT and Cursor as well as Claude?

Yes. Once Prisma Cloud is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Prisma Cloud once and every client picks it up.

### What can an AI agent actually do with my Prisma Cloud data?

An agent can list and look up Prisma Cloud access keys, create or delete them, and update their status in bulk. It can check the status of cloud accounts and AWS organizations, search the account hierarchy, read adoption checks and reports, and pull compute vulnerability and risky asset trends. Short, concrete asks such as list inactive access keys work better than long sentences.

### Does connecting Prisma Cloud give the AI access to every cloud account?

No. Every call runs with the access of the person who signed in to Elaichi, so an agent sees the Prisma Cloud accounts and keys that person can already see. Elaichi can narrow that further with roles and restrictions, and it never widens what Prisma Cloud itself allows.

### Can my team share one Prisma Cloud connection?

Yes. One administrator connects Prisma Cloud with an API key and shares the connection with a team, and nobody else ever handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Prisma Cloud call.

### Can I stop an agent from deleting or changing things in Prisma Cloud?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Prisma Cloud access keys and account status while restricting creating, deleting or changing key status, on a role or on one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Prisma Cloud connection when someone leaves?

Offboarding a person in Elaichi ends their access to Prisma Cloud through every client at once. A shared Prisma Cloud connection keeps working for everyone else on the team. If you disconnect Prisma Cloud in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.

### Does the Prisma Cloud MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Prisma Cloud is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Prisma Cloud?

Yes. Both let Claude, ChatGPT or Cursor use Prisma Cloud. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Prisma Cloud call.

### How is Elaichi different from Composio for Prisma Cloud?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Prisma Cloud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 629 Prisma Cloud tools

Every tool below is callable through https://api.elaichi.ai/mcp once Prisma Cloud is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Prisma Cloud access keys** (List). List Access Keys. Returns all access keys for your tenant if you have a Prisma Cloud System Admin role. Returns just your access keys if you don't have this role.
- **Create a Prisma Cloud access key** (Create). Add Access Key. Adds a new access key for the current user. If you have API access, you can create up to two access keys. If you want to create an access key for an existing Prisma Cloud service account instead of for the current user, then specify the name of the existing service account as the value for the request body parameter serviceAccountName. Required: name.
- **Get single Prisma Cloud access key by ID** (Get). Get Access Key by ID. Returns the metadata of the access key that has the specified ID. Required: id.
- **Delete a Prisma Cloud access key by ID** (Delete). Delete Access Key. Deletes the access key that has the specified ID. Required: id.
- **Prisma Cloud access keys status bulk update** (Update). Update Access Key Status. Activates or deactivates the access key that has the specified ID. You cannot activate an expired access key. Required: access_keys_id, status.
- **Prisma Cloud access page search** (Search). Get Permissions Access Next Page. Given a request parameter pageToken, returns the next page of permissions data. You can find the value for pageToken from the response object of a previous request to Get Permissions Access
- **List all Prisma Cloud account acl script** (List). Generate an Azure Terraform Script. Returns an Azure Network ACL script for the given Azure Subscription ID and PCDS Tenant ID that should fix all network connectivity issues. Required: subscriptionId.
- **Get single Prisma Cloud account awsorg by ID** (Get). Fetch Master Account Details (AWS Org). Returns the necessary attributes that define the AWS ORG account necessary for various PCDS flows. Required: id.
- **List all Prisma Cloud account awsorg status** (List). Performs a Permissions Check for the Given PCDS Account (AWS Org). Returns details pertaining to the rudimentary permissions check - contains details pertaining to any missing permissions. Required: awsorg_id.
- **List all Prisma Cloud account config status** (List). Get Account Status. Returns the list of Prisma Cloud Security Capabilities whose status is either warning or error for the specified account ID. The response also contains suggestions to remediate the error or warning. Required: accountId.
- **List all Prisma Cloud account status** (List). Performs a Permissions Check for the Given PCDS Account. Returns details pertaining to the rudimentary permissions check - contains details pertaining to any missing permissions. Required: account_id.
- **Get single Prisma Cloud account storage uuid by ID** (Get). Fetch Account Config By Storage UUID. Returns the account config details for the specified storage UUID. Required: id.
- **Prisma Cloud accounts ancestors search** (Search). List Ancestors (GCP). Lists the ancestors of the given projects and folders for the specified cloud account ID. A successful response returns an array of projects and/or folders each of which is mapped to an array of ancestor resource IDs. Required: cloud_type, account_id, resourceIds.
- **List all Prisma Cloud accounts hierarchy** (List). Get Saved Resource Hierarchy (GCP). Get the previously saved resource hierarchy for the specified cloud account ID. Required: cloud_type, account_id.
- **List all Prisma Cloud adoption checks** (List). Get Adoption Check Score. Returns data about the Prisma Cloud capabilities you've adopted and identifies available capabilities not yet utilized.
- **Prisma Cloud adoption compute discovered secured search** (Search). Get Discovered and Secured Resources. Get resources detected by Cloud Discovery as well as the resources secured by deployed defenders.
- **Prisma Cloud adoption compute vulnerabilities trend search** (Search). Get Vulnerabilities Trend. Get vulnerabilities discovered and resolved over time across images, hosts, functions, and containers for the impacted resources.
- **Prisma Cloud adoption cspm riskyasset trend search** (Search). Get Assets with Alerts. Get the list of assets generating alerts.
- **List all Prisma Cloud adoption report** (List). Get Adoption Advisor Report Configs.
- **Create a Prisma Cloud adoption report** (Create). Create Adoption Advisor Report Config. Required: emailIds, enabled, name, schedule, widgetDays.
- **Update a Prisma Cloud adoption report by ID** (Update). Update Adoption Advisor Report. Required: id, emailIds, enabled, name, schedule, widgetDays.
- **Delete a Prisma Cloud adoption report by ID** (Delete). Delete Adoption Advisor Report. Required: id.
- **List all Prisma Cloud adoption report download** (List). Download Latest Adoption Advisor Report. Required: reportId.
- **List all Prisma Cloud adoption report download by created on** (List). Download Adoption Advisor Report. Required: reportId, createdOn.
- **Create a Prisma Cloud adoption report generate** (Create). Create and Get an Adoption Advisor Report on demand. Required: emailIds, enabled, name, schedule, widgetDays.
- **List all Prisma Cloud alert** (List). List Alerts - GET. Returns a list of alerts that match the constraints specified in the query parameters. Max 10k results. To get more, use List Alerts V2 - GET. Data in the response object does not include alert rules. Also, in the response object: Property riskDetail is deprecated. Property resource.cloudServiceName is populated only for alerts whose resources belong to a cloud service. Required: timeType, timeAmount, timeUnit, detailed.
- **Prisma Cloud alert search** (Search). List Alerts - POST. Returns a list of alerts that matches the constraints specified in the body parameters. Max 10k results. To get more, use List Alerts V2 - POST. The fields body parameter allows you to request specific fields from the alert payload. These fields are separate from the filters you specify. The following are valid fields items.
- **Get single Prisma Cloud alert by ID** (Get). Alert Info. Returns information about an alert for the specified ID. In the response object, field riskDetail is deprecated. Required: id.
- **Create a Prisma Cloud alert aggregate** (Create). Group by Policy field. Return paginated groups with alert count based on the group by policy field, input filter along with next pagination token
- **Get single Prisma Cloud alert count by ID** (Get). Get Alerts Count By Status. Returns an alert count for the specified status. Rate Limits The following rate limits apply: Request rate limit: 2/sec Burst limit: 10/sec Required: id.
- **Create a Prisma Cloud alert CSV** (Create). Submit Alert CSV Generation Job. Submits a job to generate an alerts list that matches the constraints in the body parameters and is downloadable as a CSV file. Returns the job ID and job submission status. Filter model fields specific to pagination (sortBy, limit, and pageToken) do not apply to this request, even though the body parameters include them.
- **List all Prisma Cloud alert CSV download** (List). Download Alert CSV. Downloads the alert list that Prisma Cloud generated for the specified job ID, in CSV format. Required: csv_id.
- **List all Prisma Cloud alert CSV status** (List). Get Alert CSV Job Status. Returns the status of an alert CSV generation job with the specified job ID. Required: csv_id.
- **Create a Prisma Cloud alert dismiss** (Create). Dismiss Alerts. Dismisses one or more alerts on the Prisma Cloud platform. If the caller specifies a dismissal time range, then alerts will snooze for that time period rather than be dismissed. Required: filter.
- **List all Prisma Cloud alert graph** (List). Alert Evidence Graph. Given an alert-id in the query the API returns the data that can be presented in a graphical format. The returned response matches the JSON Graph Format standard Required: v1_id.
- **Create a Prisma Cloud alert job** (Create). Submit Job to List Alerts. Submits a job to generate an alerts list that matches the constraints in the body parameters and is downloadable in JSON format. Returns the job ID and job submission status. Filter model fields specific to pagination (sortBy, limit, and pageToken) do not apply to this request, even though the body parameters include them.
- **List all Prisma Cloud alert jobs download** (List). Download Alerts List JSON. Downloads the generated alerts list in JSON format for the specified job ID. Required: jobs_id.
- **List all Prisma Cloud alert jobs status** (List). Get Alerts List Job Status. Get the status of the alerts list job with the specified job ID Required: jobs_id.
- **List all Prisma Cloud alert policy** (List). List Alert Counts By Policy - GET. Returns alert counts grouped by policy. You can use query parameters to narrow the response. In the response object: Property alertRules is not populated. Property riskDetail is deprecated. Property resource.cloudServiceName is not populated. Rate Limits The following rate limits apply: Request rate limit: 1/sec Burst limit: 5/sec
- **Prisma Cloud alert policy search** (Search). List Alert Counts By Policy - POST. Returns alert counts grouped by policy. You can use body parameters to narrow the response. In the response object: Property alertRules is not populated. Property riskDetail is deprecated. Property resource.cloudServiceName is not populated. Rate Limits The following rate limits apply: Request rate limit: 1/sec Burst limit: 5/sec
- **Create a Prisma Cloud alert policy** (Create). Return policy with alert count. Return paginated policy with alert count based on the input filter along with next pagination token
- **Prisma Cloud alert remediation search** (Search). List Alert Remediation Commands. Generates and returns a list of remediation commands for the specified alerts and policies. Data returned for a successful call include fully constructed commands for remediation. This request requires the following filter request body parameters: filter.timeRange.type filter.timeRange.value The rest of the filter parameters are ignored. Required: filter.
- **Prisma Cloud alert remediation partial update** (Update). Remediate Alert. Remediates the alert with the specified ID if that alert is associated with a remediable policy. Required: remediation_id.
- **Create a Prisma Cloud alert reopen** (Create). Reopen Alerts. Sets the status of one or more dismissed or snoozed alerts on the Prisma Cloud platform to open. Required: filter.
- **List all Prisma Cloud alert rule** (List). List Alert Rules V2. Returns all alert rules you have permission to see based on your role. The data returned does not include an open alerts count. This request does not return a populated alertRuleNotificationConfig property in the response object. Use Get Alert Rule by ID to retrieve a response that includes a populated alertRuleNotificationConfig property.
- **Create a Prisma Cloud alert rule** (Create). Add an Alert Rule. Adds a new alert rule. By default, all alerts that this alert rule triggers will display on the Alerts page. You can also send Prisma Cloud alerts that this alert rule triggers to one or more third-party tools that you have integrated with the Prisma Cloud service. You can also configure the alert rule to send email notifications. Required: name, target.
- **Get single Prisma Cloud alert rule by ID** (Get). Get Alert Rule by ID. Returns information about the alert rule with the specified ID. Required: id.
- **Update a Prisma Cloud alert rule by ID** (Update). Update Alert Rule. Updates information about the alert rule that has the specified ID. Required: id, name, target.
- **Delete a Prisma Cloud alert rule by ID** (Delete). Delete Alert Rule. Deletes the alert rule that has the specified ID. Required: id.
- **List all Prisma Cloud alert suggest** (List). List Alert Filters. Returns an object whose keys are the available policy filters. The corresponding values are default or recently set filter options
- ...and 579 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
