Hosted MCP for Cursor & Claude

Expose deployed Viksa agents to MCP clients over HTTPS — no local stdio bridge required. Uses Streamable HTTP at https://api.viksaai.com/mcp.

Overview

  • User-scoped MCP tokens — you create and revoke your own mcp_ tokens (like a GitHub PAT).
  • No project ID in the URL — tenant context (account_id, org_id, project_id) is embedded in the token.
  • Scopes — mcp:read (discover tools/resources), mcp:execute (call tools).
  • Tracing — MCP calls are traced with source MCP Call and your user email.

Cursor configuration

Pass your mcp_ token in the Authorization header (same pattern as GitHub Copilot MCP). The easiest approach is to paste the token directly into ~/.cursor/mcp.json on your machine.

Option A — Token in mcp.json (recommended)

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). Replace mcp_... with your key, then fully quit and restart Cursor.

JSON
{
  "mcpServers": {
    "viksa": {
      "url": "https://api.viksaai.com/mcp",
      "headers": {
        "Authorization": "Bearer mcp_..."
      }
    }
  }
}

Other options

Option B — envFile

Keep the token in a separate file instead of mcp.json:

cURL
VIKSA_MCP_TOKEN=mcp_...
JSON
{
  "mcpServers": {
    "viksa": {
      "url": "https://api.viksaai.com/mcp",
      "envFile": "~/.viksa-mcp.env",
      "headers": {
        "Authorization": "Bearer ${env:VIKSA_MCP_TOKEN}"
      }
    }
  }
}

Option C — Environment variable (macOS)

On macOS, Cursor launched from the Dock does not read ~/.zshrc. Use launchctl setenv so $${env:VIKSA_MCP_TOKEN} resolves at startup:

cURL
# macOS — Cursor launched from the Dock does not read ~/.zshrc
launchctl setenv VIKSA_MCP_TOKEN "mcp_..."
JSON
{
  "mcpServers": {
    "viksa": {
      "url": "https://api.viksaai.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VIKSA_MCP_TOKEN}"
      }
    }
  }
}

Never commit mcp_ tokens to git. ~/.cursor/mcp.json is local-only and safe for a pasted token. Revoke unused keys from Keys → MCP Keys in the console.

Single-agent URL (optional)

Convenience URL when you only need one agent. Token policy must allow that agent_alias.

JSON
{
  "mcpServers": {
    "viksa-demo": {
      "url": "https://api.viksaai.com/mcp/agents/demo_agent",
      "headers": {
        "Authorization": "Bearer mcp_..."
      }
    }
  }
}

Refresh behavior

Gateway tool registry — cached for about 60 seconds. New deployments or endpoint changes appear on the next tools/list after cache expiry.

Cursor tool list — refreshes when you reconnect the MCP server (toggle off/on in MCP settings or restart Cursor), not on a fixed timer.

Your token — static until you revoke or rotate it in the Viksa console under Keys → MCP Keys.

Create a token

In the Viksa console, open your project → Keys → MCP Keys → Create. The full secret is shown once; copy the ready-to-paste Cursor config immediately.