Evo by Snyk
Evo by Snyk's official MCP server connects agents to your Evo tenant — AI assets (models, agents, MCP servers, skills, repositories, developer machines), the relationships between them, policies, and the issues they raise. It is a hosted server over streamable HTTP; nothing runs on your machine. The default endpoint is https://evo.snyk.io/mcp.
This is a different product from the Snyk CLI's local MCP server, which scans code. Evo covers your organization's AI estate and the policies that govern it.
Setting up
-
In Willow, go to MCP Servers → + Add MCP server and find the Evo by Snyk card with the Official badge.
-
Click + Use. If your Evo tenant is not in the default region, set Evo host to your region's host (see the table below), then complete the OAuth prompt as a Snyk user whose Tenant role includes Evo access.
Willow registers itself with Evo automatically using dynamic client registration — no app or client ID to create beforehand.
Evo host
| Region | Evo host |
|---|---|
| Default, SNYK-US-01 | evo.snyk.io |
| SNYK-US-02 | evo.us.snyk.io |
| SNYK-EU-01 | evo.eu.snyk.io |
| SNYK-AU-01 | evo.au.snyk.io |
For a single-tenant deployment, add the evo. prefix to the hostname supplied for your deployment, for example evo.your-deployment-hostname. Don't use the API hostname.
Permissions
The agent runs as the Snyk user who authorizes it, with that user's Tenant role. Read access gives the read tools for assets, relationships, policies, and issues. Users with write access also get tools to create and update custom policies and to change the MCP server allow list. Write tools are not listed for users who can't use them, and they ask for approval in the client, so use a client that supports MCP elicitation for those.
Evo's server doesn't support delete actions, but write tools can still change how Evo behaves, for example by updating a policy's conditions or removing a server from the allow list. Review each change before you approve it.
Troubleshooting
The request returns HTTP 401
The access token is missing, expired, or invalid. Reconnect the connector in Willow to run the OAuth flow again. Also check that the Evo host matches your tenant's region.
A tool call returns permission_denied
Your Tenant role doesn't include Evo access. Ask your Snyk Tenant Admin to assign a role with Evo access, then reconnect.
The write tools return unsupported_client
The client can't ask you to approve policy changes. The read tools still work.
The request returns HTTP 429
You exceeded Evo's per-user rate limit, which is shared across every client in the same region. Wait the number of seconds in the Retry-After header, then retry.