Gecko Security
Day 3 after signup
MCP, service accounts, and repository access
Why it works
- Lead with a concise overview of what changed, then give each major update its own section so readers can scan and explore relevant features.
- Put smaller changes in a compact list to show breadth without distracting from the main announcements.
- A personal introduction and founder sign-off make a product changelog feel direct and human.
How it is built
- Dated update header
- Personal introduction
- Featured product changes
- Additional updates list
Email copy
October 23, 2026 What's new in Gecko Hi, Artemiy here. Three changes shipped since our last update, plus a few smaller ones below. Gecko, headless Gecko now has an MCP server. Connect Claude, ChatGPT, Codex, Cursor, or any MCP client to pull findings, triage them, and file tickets without opening the dashboard. Teams use it to run Gecko headless from their agents and CI. Every call is limited to your Gecko role. Set up MCP Service accounts Service accounts give CI pipelines and internal tools an API token owned by the team, not a person. The token keeps working when someone changes roles or leaves. Create a service account Repository access Gecko can now follow your GitHub and GitLab permissions. Turn it on and each member of your team sees only the repositories they can push to, across findings, scans, exports, and API keys. Turn on repository access Also new · SARIF vulnerability exports · Outbound webhooks · DefectDojo, Wiz, and Snowflake integrations · Scan a specific commit from the API · Command palette and Ask Gecko (⌘K) Open Gecko Artemiy CTO & Co-founder, Gecko Security You're receiving this because you use Gecko. Unsubscribe Gecko Security, Inc. · 4283 Express Ln, Suite GB12463, Sarasota, FL 34249