mcp

Connect VS Code & others

Zaai Dev is a standard stdio MCP server, so any MCP-capable client can run it. The launch command is always the same — only where the config lives differs.

VS Code

VS Code reads MCP servers from a .vscode/mcp.json file in your workspace (or your user settings). Use the servers key:

.vscode/mcp.json

{
  "servers": {
    "zaai-dev": {
      "command": "npx",
      "args": ["-y", "@zaai-dev/mcp"],
      "env": {
        "ZAAI_API_TOKEN": "zaai_mcp_YOUR_SECRET_HERE"
      }
    }
  }
}

Any other MCP client

Most clients (Claude Desktop, Windsurf, and others) use an mcpServers object. The command, args, and env are identical — only the wrapper key and file location change:

mcp config

{
  "mcpServers": {
    "zaai-dev": {
      "command": "npx",
      "args": ["-y", "@zaai-dev/mcp"],
      "env": {
        "ZAAI_API_TOKEN": "zaai_mcp_YOUR_SECRET_HERE"
      }
    }
  }
}

the constant

Whatever the client, the server is npx -y @zaai-dev/mcp with ZAAI_API_TOKEN in the environment. Check your client's MCP docs for exactly where its config file lives, then drop in the block above.

Need a token? See Authentication & tokens. Trouble connecting? See MCP troubleshooting.