Build powerful and secure agents powered by Starknet
Snak MCP server exists for a simple reason — assistants are far more useful when they can act on Snak directly instead of describing what you should do. Build powerful and secure agents powered by Starknet.
Once Snak is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — The Configuration tool exposed by this serverThe server ships on npm as @snakagent, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 8 environment variables: API_KEY, STARKNET_PRIVATE_KEY, YOUR_STARKNET_PRIVATE_KEY, STARKNET_RPC_URL, YOUR_STARKNET_RPC_URL, OPENAI_API_KEY, YOUR_OPENAI_API_KEY, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Snak's toolset — Prerequisites, Installation, Configuration — is a fair guide to whether it matches your workflow. It is maintained by KasarLabs; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Snak's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"snak": {
"command": "npx",
"args": ["-y", "@snakagent"],
"env": {
"API_KEY": "your-value",
"STARKNET_PRIVATE_KEY": "your-value",
"YOUR_STARKNET_PRIVATE_KEY": "your-value",
"STARKNET_RPC_URL": "your-value",
"YOUR_STARKNET_RPC_URL": "your-value",
"OPENAI_API_KEY": "your-value",
"YOUR_OPENAI_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| API_KEY | Credential the server authenticates with. | Yes |
| STARKNET_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| YOUR_STARKNET_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| STARKNET_RPC_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_STARKNET_RPC_URL | Endpoint or connection string the server talks to. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.