Semgrep vs Sregymgate MCP
A side-by-side look at the Semgrep and Sregymgate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Semgrep for security work as a local process; choose Sregymgate MCP for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Semgrep when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Sregymgate MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
run_incident_replay, score_sre_agent, export_incident_verdict.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 17,186 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Semgrep | View Sregymgate MCP |
Tools & capabilities
Semgrep tools
No tool names declared yet. Check the project README from the listing page.
Sregymgate MCP tools 4
run_incident_replayscore_sre_agentexport_incident_verdictcompare_runbook_versions
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Semgrep
{
"mcpServers": {
"semgrep-semgrep": {
"command": "uvx",
"args": [
"semgrep"
]
}
}
}
Sregymgate MCP
{
"mcpServers": {
"sregymgate-mcp": {
"url": "https://sregymgate.clauxel.com/mcp"
}
}
}
Frequently asked questions
Semgrep is categorized under Security and uses a local stdio subprocess. Sregymgate MCP belongs to Security and uses a remote HTTP/SSE transport. Pick Semgrep for security work and Sregymgate MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Semgrep is listed as free. Auth: no auth required. Sregymgate MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add semgrep-semgrep and sregymgate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Semgrep has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 17,186 GitHub stars. Sregymgate MCP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.