Cursor

Cursor uses an mcp.json file with a top-level mcpServers key. The file location determines whether the configuration applies to a single project or globally across all projects.

Project Scope

For the configuration to work just within one project, create .cursor/mcp.json in the project root. This is useful if you wish to maintain multiple similar projects and define a different API key in each, e.g. if you have scoped the API key for a specific Veyo Project. This ensures the MCP will query the correct Veyo project.

{
  "mcpServers": {
    "veyo-mcp": {
      "command": "npx",
      "args": ["-y", "@darkloop/veyo-mcp@latest"],
      "env": {
        "VEYO_API_URL": "https://portal.veyomcp.com",
        "VEYO_API_KEY": "YOURAPIKEYHERE"
      }
    }
  }
}

User Scope

This is the most simple, as it will add Veyo tools automatically to any project you open in Cursor, however it will always query the same Veyo project. To easily switch projects, modify the "Default Project" on your Veyo dashboard to match the dev project you're working on.

Create the file at ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json) with the same JSON contents as above.

After saving, open Settings (Ctrl+Shift+J) → Features → Model Context Protocol to confirm the server is listed/enabled, or run cursor-agent mcp list if using Cursor CLI.