Semgrep MCP connector
The Semgrep connector brings your Semgrep findings, issues, deployments and ignore rules into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can search, triage and update them under their own Semgrep access with every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List open Semgrep findings for the platform deployment.
Working in Semgrep with Elaichi
-
List all Semgrep agent deployments
-
Get single Semgrep agent deployment by ID
-
Semgrep agent deployments list tags
How to connect Semgrep to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Semgrep 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.
Semgrep 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.
Semgrep 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.
Semgrep 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.
Semgrep 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 Semgrep 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 Semgrep through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Semgrep is logged.
-
Security
Triage new findings before standup
Ask for the Semgrep findings that appeared overnight, grouped by severity and repository, and mark the ones that are already handled as resolved in one pass.
-
Engineering
Understand an issue before fixing it
Pull up a single Semgrep issue by its ID, read the rule that flagged it and the line it points at, and get a plain explanation of why it matters before opening the file.
-
Security
Clear false positives in bulk
When a rule keeps flagging test fixtures, search for every matching finding and update them together instead of clicking through each one in the Semgrep dashboard.
-
Platform
Keep ignore rules tidy
List the ignores set on a Semgrep deployment, spot the ones that are stale or too broad, and update or remove them together so real problems stop being hidden.
-
Compliance
Report open issues by severity
Search Semgrep issues across a deployment and summarize how many are open, how old they are and which repositories carry the most, ready to paste into an audit response.
-
Engineering management
Check which repositories are covered
Review each Semgrep deployment, its tags, its notification rules and whether the GitHub app is connected, so you know which teams are actually being scanned.
Try asking
- “List open Semgrep findings for the platform deployment.”
- “Which notification rules are set on our Semgrep deployment?”
- “Summarize Semgrep findings created in the last 14 days.”
What connecting Semgrep gets you
6 screens from Elaichi, each doing one job for your Semgrep account.
Ask Elaichi to work across your apps.
List open Semgrep findings for the platform deployment.
Which notification rules are set on our Semgrep deployment?
Summarize Semgrep findings created in the last 14 days.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Semgrep findings in plain language.
Starter prompts return answers from live Semgrep findings, deployments and notification rules.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Semgrep here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
208 Semgrep tools are ready to call.
Deployments, findings, actions, tags and user roles, with no custom code written.
Toolboxes
Each team gets its own Semgrep toolbox.
Curate one toolbox for AppSec findings and another for platform deployments.
Shared connections
Teammates use Semgrep without seeing a token.
Connections show who connected each Semgrep account and which teams and members share it.
Audit log
Every Semgrep call is written down.
When, who, what happened, type and resource for each finding update and deployment change.
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.
Semgrep digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch findings
Semgrep
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
Semgrep
Queued
Automations
A schedule turns Semgrep findings into a digest.
Six steps fetch findings, group them, draft a digest, get approval, post back.
Semgrep health
Refreshed 4 minutes ago · every 15 minutes · from the findings collection
Findings
1,284 ↓ 12%
Deployments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Findings created
Last 14 days
By team
Share of activity
AppSec 34%
Platform 27%
Backend 21%
Compliance 18%
Collections and dashboards
Semgrep findings counted, not asked about.
Four metrics, 14 days of findings created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Semgrep
All three can connect Semgrep 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 Semgrep tools | Allow or restrict single Semgrep 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 Semgrep 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.
Semgrep tools for your AI agents
208 tools are ready to call through Elaichi's MCP endpoint the moment you connect Semgrep, 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 Semgrep to Claude?
Connecting Semgrep to Claude takes two steps. First, connect Semgrep in Elaichi by pasting an API key from your Semgrep account settings, there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs in through Elaichi and your Semgrep findings, issues and deployments are available.
Does Semgrep work with ChatGPT and Cursor as well as Claude?
Yes. Once Semgrep is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Semgrep once and every client you use picks it up.
What can an AI agent actually do with my Semgrep data?
With Semgrep connected, an agent can search your findings and issues, open a single issue to explain what the rule caught, and update a batch of findings after you have triaged them. It can also list your Semgrep deployments, their tags and notification rules, check whether the GitHub app is connected, and create, update or remove ignore rules and deployment actions. Because Semgrep exposes a long list of actions, short concrete asks such as "open critical findings in the payments repo" work better than long paragraphs.
Does connecting Semgrep give the AI every deployment and every finding?
No. When someone connects Semgrep, the agent works within that person's own Semgrep access, so it sees the deployments and findings they can already see in Semgrep and nothing more. Elaichi can narrow that further, for example to read-only or to a single deployment, but it can never widen it beyond what Semgrep itself grants.
Can I stop an agent from deleting ignore rules or changing findings in Semgrep?
Yes. Restrictions in Elaichi work per action, so you can allow searching Semgrep findings and issues while restricting updates to findings, deletion of ignore rules or changes to deployment actions. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Semgrep connection when someone leaves?
When a person is offboarded in Elaichi, their access to Semgrep through every connected client ends at once. If they had shared a Semgrep connection with a team, it keeps working for everyone else on that team. Disconnecting Semgrep once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in the same step.
Does the Semgrep MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Semgrep 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 Semgrep?
Yes. Both let Claude, ChatGPT or Cursor use Semgrep. 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 Semgrep call.
How is Elaichi different from Composio for Semgrep?
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 Semgrep: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Semgrep 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