Connect Snyk to Claude Code
Read organizations, projects, targets, security issues, SBOMs, and scan settings. Add Toolspoke to Claude Code once and it can use 9 Snyk actions. Your Snyk credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Snyk and connect it
Add Snyk to a project in your Toolspoke workspace.
API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- API token
- Snyk → your account settings → General → Auth Token, or a service account token from Group or Organization settings. Sent as "Authorization: token <value>", which is Snyk's own format and not a bearer token. A token is tied to one region.
Choose what Claude Code may do
All 9 actions only read, and any of them can be switched off for a project.
What you can ask Claude Code for
A few of the Snyk actions that only read, so they are safe to try first.
- List the organizations this token can see, with each one's id, name and slug
- Return the user or service account this token belongs to
- List an organization's security issues
- Read whether Snyk Code is enabled for an organization, and how it is configured
What Claude Code can do in Snyk
9 actions read.
Reads
List organizations
List the organizations this token can see, with each one's id, name and slug. Call it first when you do not know which organization to act on, and to find out whether the connection reaches anything at all. The id returned here is the UUID every org_id argument below takes, not the slug shown in the Snyk URL bar.
Get self
Return the user or service account this token belongs to. Call it to confirm whose access the connection is acting with before reading anything else.
List projects
List an organization's projects, each one is a single manifest or image Snyk monitors, with its name, type, origin, target reference and business criticality. Pass meta_latest_issue_counts to get the open issue counts per project in the same call, which is usually the fastest way to find what is worth looking at.
Get project
Fetch one project by id, its name, type, origin, target file and reference, tags, business criticality, environment and lifecycle. The target it belongs to is always embedded, so this answers which repository or image the project came from without a second call. Pass meta_latest_issue_counts for its open issue counts.
List issues
List an organization's security issues. To see one project's issues, pass its UUID as scan_item_id, the API filters by scan item rather than by a project_id parameter, and this operation supplies the matching scan_item.type for you. Each issue carries its title, type, effective severity, status, and the file path, line and commit where it was found. The response is not written to the audit log: a list of unfixed vulnerabilities with the file each one lives in is the single most useful thing an attacker could read out of a transcript.
Get issue
Fetch one issue by id, its title and description, severity, the problems it maps to (CVE, CWE, Snyk rule), its coordinates in the codebase or dependency tree, and any recorded resolution. The response is not written to the audit log, for the same reason list_issues is not.
List targets
List an organization's targets, the repositories, images and other sources Snyk imports projects from, with each one's display name, URL and origin. A target is the thing you connected; a project is one manifest inside it. Pass exclude_empty to skip targets that produced no projects.
Get project sbom
Fetch a project's software bill of materials, every dependency Snyk resolved for it, with versions and, unless excluded, licences. This is the closest thing the REST API has to a dependency listing: Snyk publishes no REST endpoint that lists dependencies, only this document and a count on the projects endpoints. The response is not written to the audit log, because a complete versioned dependency inventory is a map of what a project is vulnerable to.
Get sast settings
Read whether Snyk Code is enabled for an organization, and how it is configured. Snyk has no single org-settings endpoint, settings are split by product, so this is the Code one; the equivalent IaC and secrets settings live on sibling paths this connector does not expose. Use it to check that a clean Code report means scanning was actually on.
Snyk in Claude Code: questions
Does Claude Code see my Snyk credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Will 9 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Snyk action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Snyk call does not run in a sandbox, so it bills nothing.
Snyk in your other apps
Try Snyk in Claude Code
Free to start, and tool calls cost nothing on any plan.