Skip to content

MCP Server

The state of the Zavu MCP server, what works in it today, and what to use instead to give a coding agent the Zavu API.

View .md

What it is

@zavudev/sdk-mcp is a Model Context Protocol server for Claude, Cursor, Codex and other MCP clients. It exposes two tools rather than one per endpoint:

ToolWhat it doesWorks today
search_docsSearches the SDK documentation, so the agent looks up a parameter instead of guessing it.Only with --docs-search-mode=local
executeRuns TypeScript against an authenticated Zavu client, so the agent can chain calls.Only with --code-execution-mode=local and Deno 2.6 or earlier installed

Running it locally

If you want to use it before the rebuild, run both tools on your own machine. search_docs then works as is; execute needs Deno 2.6 or earlier on your PATH (later Deno versions exit before the tool is ready).

terminal
export ZAVUDEV_API_KEY="your_key" npx -y @zavudev/sdk-mcp@latest --code-execution-mode=local --docs-search-mode=local

Add it to a client with the same arguments. Claude Code:

terminal
claude mcp add zavudev --scope user -e ZAVUDEV_API_KEY="your_key" -- \ npx -y @zavudev/sdk-mcp --code-execution-mode=local --docs-search-mode=local

Clients that read a JSON config (Claude Desktop, Cursor ~/.cursor/mcp.json, Windsurf ~/.codeium/windsurf/mcp_config.json) take the same command:

JSON
{ "mcpServers": { "zavudev": { "command": "npx", "args": ["-y", "@zavudev/sdk-mcp", "--code-execution-mode=local", "--docs-search-mode=local"], "env": { "ZAVUDEV_API_KEY": "your_key" } } } }

VS Code reads the same object under servers in .vscode/mcp.json, with "type": "stdio".

Learn More