Installation Instructions

Before you start

You need:

1. A Veeqo account with the permissions for whatever you intend to do (read vs. write tools are gated by your Veeqo role).
2. For clients that don't yet speak remote MCP natively: Node.js 18+ (provides npx, used to run the mcp-remote adapter).
3. Your Veeqo API key

Connection details

You can set up the MCP with any AI assistant using these connection details.

Property	Value
Server URL	https://app.veeqo.com/mcp
Transport	Streamable HTTP (remote)
Authentication	OAuth 2.0 Authorization Code + PKCE (browser login to Veeqo)
Alternative auth	Authorization: Bearer apikey:<your-veeqo-api-key> (programmatic / non-OAuth clients)

Read below for instructions on connecting with some of the most common AI assistants. Use https://app.veeqo.com/mcp as the server URL in every example below.

Claude

Claude supports remote MCP servers natively through Custom Connectors, which is the cleanest path because it handles the OAuth login for you.

Option A — Claude Desktop / Claude.ai (Custom Connector — recommended)

1. Open Claude (Desktop app or claude.ai).
2. Go to Settings → Connectors.
3. Click Add custom connector.
4. Name it Veeqo and paste the URL: https://app.veeqo.com/mcp
5. Click Add, then Connect. A browser window opens to the Veeqo login page.
6. Sign in to Veeqo and approve access. Claude stores the session and the Veeqo tools become available.

Custom Connectors are available on Claude Pro, Max, Team, and Enterprise plans. If you don't see the option, update to the latest Claude Desktop or use Option B.

Option B — Claude Desktop via config file (mcp-remote fallback)

Use this if your Claude Desktop version only supports local (stdio) servers. The mcp-remote adapter bridges the remote server and handles OAuth.

Edit claude_desktop_config.json:

1. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
2. Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "veeqo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.veeqo.com/mcp"]
    }
  }
}

Restart Claude Desktop. On first use a browser opens for the Veeqo OAuth login.

Option C — Claude Code (CLI)

claude mcp add --transport http veeqo https://app.veeqo.com/mcp

Then start Claude Code and run /mcp to trigger the OAuth login. Use claude mcp list to confirm the server is connected.

Cursor

Add the server to ~/.cursor/mcp.json (global) or <project>/.cursor/mcp.json (project-scoped):

{
  "mcpServers": {
    "veeqo": {
      "url": "https://app.veeqo.com/mcp"
    }
  }
}

Open Cursor Settings → MCP. The veeqo server appears with a Needs login prompt — click it to complete the Veeqo OAuth flow in your browser. Once authorised the indicator turns green and the tools are listed.

VS Code (GitHub Copilot — Agent mode)

Create .vscode/mcp.json in your workspace (or add to user settings via the command palette → MCP: Add Server):

{
  "servers": {
    "veeqo": {
      "type": "http",
      "url": "https://app.veeqo.com/mcp"
    }
  }
}

Open the Copilot Chat view, switch to Agent mode, and start the veeqo server. VS Code prompts you to authenticate via the browser. Use the tools icon in Agent mode to confirm the Veeqo tools are available.

Cline (VS Code / JetBrains extension)

1. Open the Cline panel and click the MCP Servers icon → Remote Servers.
2. Add a server named veeqo with URL https://app.veeqo.com/mcp.

Or edit cline_mcp_settings.json directly:

{
  "mcpServers": {
    "veeqo": {
      "type": "streamableHttp",
      "url": "https://app.veeqo.com/mcp"
    }
  }
}

Cline opens a browser for the Veeqo OAuth login on first connect.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "veeqo": {
      "serverUrl": "https://app.veeqo.com/mcp"
    }
  }
}

In Windsurf, open Cascade → MCP (the hammer/plugins icon) and click Refresh. Authenticate via the browser when prompted.

If your Windsurf version doesn't support serverUrl, fall back to the mcp-remote command form shown in the Generic fallback section below.

ChatGPT

Remote MCP connectors are available in ChatGPT via Developer mode / Connectors (Plus, Pro, and Business/Enterprise plans where enabled by the workspace admin).

1. Settings → Connectors (enable Developer mode if required).
2. Add / Create a connector.
3. Set the MCP server URL to https://app.veeqo.com/mcp.
4. Choose OAuth as the authentication method and complete the Veeqo login.

Connector availability and the exact menu names change between ChatGPT releases and depend on workspace admin settings. If MCP connectors aren't enabled for your account, this path won't be available.

Generic fallback (any stdio-only MCP client)

Any client that supports local (stdio) MCP servers can reach the remote server through the mcp-remote adapter:

{
  "mcpServers": {
    "veeqo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.veeqo.com/mcp"]
    }
  }
}

Authenticating with a Veeqo API key instead of OAuth

For non-interactive / programmatic clients, you can pass a Veeqo API key directly instead of doing the browser OAuth flow.

To get your API key:

1. Go to Settings.
2. Click on Users.
3. Click on the relevant user and copy your API key.

Important

If you haven't used the API key before you may need this enabled in your account by contacting the Support team. For more information on the API key and best practices, see Generating your API keys.

Once you have your API key, forward it as a bearer token with the apikey: prefix:

{
  "mcpServers": {
    "veeqo": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://app.veeqo.com/mcp",
        "--header", "Authorization: Bearer apikey:${VEEQO_API_KEY}"
      ],
      "env": { "VEEQO_API_KEY": "your_veeqo_api_key" }
    }
  }
}

The server validates the key against Veeqo on every request, so a revoked key stops working immediately.