Wiz MCP connector
The Wiz connector brings Wiz issues, vulnerability findings, detections, projects, exposed resources and reports into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can ask about cloud security posture in plain language.
- App credentials
- Free 14-day trial
- No credit card
Show critical Wiz issues opened this week by project
Working in Wiz with Elaichi
-
List all Wiz users
-
List all Wiz projects
-
List all Wiz audit logs
How to connect Wiz to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Wiz MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Wiz MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
Wiz MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Wiz MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Wiz MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Wiz to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Wiz through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Wiz is logged.
-
Security
Triage this morning's critical issues
Ask which Wiz issues opened overnight at critical severity, which projects they touch and whether any resource is publicly exposed, then decide who picks up what before standup.
-
Cloud engineering
Find the vulnerabilities on a workload
Pull the vulnerability findings for one cloud resource or one project and get them grouped by severity and fix availability so the patching plan writes itself.
-
DevOps
Check a repository before the release
List the code scan findings and peer review enforcement findings for a version control repository so the release owner knows what is blocking sign-off.
-
Compliance
Gather evidence for the audit
Collect the backup findings, firewall findings and infrastructure logging findings for a project into one summary that maps to the control you are being asked about.
-
IT
Review who has access to Wiz
List Wiz users and recent audit log entries to confirm that the right people hold access and to spot accounts that should have been removed.
-
Leadership
Summarize exposure for the weekly review
Ask for exposed resources, open detections and configuration findings across all projects, and get a short readout you can paste into the weekly security review.
Try asking
- “Show critical Wiz issues opened this week by project”
- “Which exposed resources have unresolved vulnerability findings?”
- “Summarize configuration findings for the payments project”
What connecting Wiz gets you
6 screens from Elaichi, each doing one job for your Wiz account.
Ask Elaichi to work across your apps.
Show critical Wiz issues opened this week by project
Which exposed resources have unresolved vulnerability findings?
Summarize configuration findings for the payments project
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Wiz issues in plain language.
Answers come from live Wiz issues, findings and projects, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Wiz.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
18 Wiz tools ready without custom code.
Issues, vulnerability findings, exposed resources, projects and audit logs, each with listed methods.
Toolboxes
Every team gets its own Wiz toolbox.
Cloud security, platform and compliance each see a toolbox scoped to their work.
Shared connections
Share a Wiz connection, never the key.
See who connected each Wiz account and which teams and members use it.
Audit log
Every Wiz call is written down.
When, who, what happened, type and resource for each request through Elaichi.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Wiz digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch issues
Wiz
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Wiz
Queued
Automations
A schedule turns Wiz issues into action.
Fetch issues, group them, draft a digest, get approval, post back to Wiz.
Wiz health
Refreshed 4 minutes ago · every 15 minutes · from the issues collection
Issues
1,284 ↓ 12%
Vulnerability findings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Issues created
Last 14 days
By team
Share of activity
Cloud security 34%
Production 27%
Compliance EMEA 21%
AppSec 18%
Collections and dashboards
Wiz health numbers land on a schedule.
Four metrics, 14 days of new findings and a team breakdown, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Wiz
All three can connect Wiz 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Wiz tools | Allow or restrict single Wiz 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 Wiz 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Wiz tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Wiz, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Wiz to Claude?
Connect Wiz in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. The Wiz sign-in step asks for the app credentials from your Wiz tenant, and there is no OAuth application to register and no client ID or secret to generate. Once both steps are done, Claude can read Wiz issues, findings and projects as you.
Does Wiz work with ChatGPT and Cursor as well as Claude?
Yes. The Wiz connector sits behind one endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent all connect to that same address. You connect Wiz once in Elaichi and every client you use picks it up.
What can an AI agent actually do with my Wiz data?
With Wiz connected, an agent can list issues, detections, vulnerability findings and configuration findings, look up projects, resources and exposed resources, and read reports and audit logs. It can also pull findings for code scans, firewalls, backups, application and infrastructure logging, and peer review enforcement, and open a single system activity by its ID. This connector reads from Wiz; it does not change anything in your Wiz tenant.
Does connecting Wiz give the AI access to every project in my tenant?
No. Every request to Wiz runs inside the access of the person who signed in, so an agent sees the projects, issues and findings that person can already see in Wiz and nothing beyond that. Elaichi can narrow that further, for example to a subset of the connector's abilities, but it can never widen what Wiz itself allows.
Can I stop an agent from deleting or changing things in Wiz?
The Wiz connector only lists and reads records, so an agent cannot delete or change issues, projects or findings through it. Beyond that, Elaichi restrictions work per action, so you can also restrict particular Wiz abilities, such as reading audit logs or user lists, for a role. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Wiz connection when someone leaves?
Offboarding a person in Elaichi ends their access to Wiz through every client at once, whether Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent. If they connected a shared Wiz connection, it keeps working for everyone else on the team. Disconnecting Wiz once in Elaichi removes it from every client, with no per-client cleanup.
Does the Wiz MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Wiz 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 Wiz?
Yes. Both let Claude, ChatGPT or Cursor use Wiz. 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 Wiz call.
How is Elaichi different from Composio for Wiz?
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 Wiz: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Wiz in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot