What does Gecko access when I connect a repo?

Repository metadata at connection, and a clone at scan time only, inside an isolated sandbox that’s destroyed when the scan completes. Write permissions exist solely to comment on pull requests and propose fixes, and they’re scoped conservatively.

Do you support GitHub Enterprise Server or self-managed GitLab?

Yes. GitHub.com and GitHub Enterprise Server, plus GitLab.com and self-managed GitLab instances, including behind your firewall via a dedicated service account.

What if our tool isn’t listed?

You can almost certainly still connect it. Gecko exposes webhooks, a full API, and an open MCP server, so any agent or automation can read findings and report fixes back. Tell us what you’re wiring up and we’ll help.

How does Gecko know a fix actually happened?

It verifies rather than trusts. Merged fix commits, closed tickets via webhook, and rescans all feed back, and a lightweight fix recheck can confirm a merge without re-running the full pipeline. If you fixed something outside the code, you can tell Gecko and it records the rationale.

Do integrations need a particular plan?

Slack notifications and API keys arrive with Pro. SSO and SCIM, audit logs, and hybrid deployment are Enterprise. Everything else follows your plan’s scan allowance.

Is it safe to give an AI agent access to security findings over MCP?

Findings go to the agent, and the agent works in your repo under the permissions you already granted it. Nothing is taken on trust: when the pull request merges or the ticket closes, Gecko rescans and confirms the fix is real. Start hands-on and loosen your grip as the fixes earn it.

Findings and Fixes Where You Work Already

Findings flow out to your repos, tickets and AI tools. When the pull request merges or the ticket closes, Gecko verifies the fix and learns from it. No integration is a dead end.

Free Trial Book a Demo

As Autonomous as You Want It to Be

Three ways to route findings, chosen per team. Start hands-on, and hand over more as the fixes earn it.

Tickets Your Team Reviews

Findings become Jira, Linear, ClickUp or Shortcut tickets with preset assignees. When a ticket closes, Gecko rescans and confirms the fix is real.

Pull Requests From Gecko

Gecko opens the PR itself: fix included, written in your codebase’s style, assigned to the reviewer you choose. Merge it and the finding is verified fixed.

Fully Agentic Over MCP

Pull findings into Claude, Codex, or Devin over MCP and let your AI workflow clear them. Gecko checks what actually got fixed. Trust, then verify.

Everything Gecko Connects To

Ticketing, chat, security dashboards, and AI agents. If your stack speaks MCP or webhooks, it works with Gecko.

Coding agents
Claude Code
Anthropic’s agentic coding tool for the terminal and IDE.
Security
Wiz
Cloud security platform for risk detection across cloud environments.
Messaging
Slack
Team messaging and workflow platform.
Issue tracking
Jira
Atlassian’s issue tracking and project management platform.
Issue tracking
Linear
Issue tracking and project planning for software teams.
Security
DefectDojo
Open-source vulnerability management and orchestration.
Security
GitLab
DevOps platform with source control, CI/CD and vulnerability reporting.
Coding agents
Codex
OpenAI’s software engineering agent.
Coding agents
Corridor.dev
AI code review that runs on your pull requests.
Coding agents
Cursor
AI-native code editor.
Coding agents
Devin
Cognition’s autonomous AI software engineer.
AI assistants
ChatGPT
OpenAI’s conversational AI assistant.
AI assistants
Claude Desktop
Anthropic’s Claude app for macOS and Windows.
Protocols
MCP
Model Context Protocol, the open standard for connecting AI tools to systems.
Issue tracking
ClickUp
Work management platform for tasks, docs and projects.
Issue tracking
Shortcut
Project management built for software teams.