MCP · beta

Connect your AI agent to viggoVet

The viggoVet MCP server lets any AI assistant securely read your clinic's data — patients and medical history, clients and balances, the calendar and free slots, invoices, inventory, dashboards and reports — over the Model Context Protocol.

Endpoint: https://mcp.viggo.vet/mcp
Transport: Streamable HTTP · Auth: per-request headers (your clinic address + credentials)

What you need

Header	Value	Required
`X-Viggo-Clinic-Url`	the address you use to log in to viggoVet, e.g. `https://demo.viggo.vet`	Yes
`X-Viggo-Api-Url`	your clinic's API address, e.g. `https://demo-api.viggo.vet` (provided by viggoVet support)	Recommended
`X-Viggo-Email`	the viggoVet login email of the user the agent acts as	Yes (today)
`X-Viggo-Password`	that user's password	Yes (today)
`X-Viggo-Token`	API token (coming soon — replaces email + password)	—

If X-Viggo-Api-Url is left out, the server works it out from your clinic address. Your viggoVet permissions are enforced on every call — the agent can never see or do more than that user's account allows.

Use a dedicated AI user. viggoVet allows one active session per user. If you connect with your normal login, you'll be signed out of the viggoVet web app while the agent is active. Ask your viggoVet admin to create a separate user for the agent, with only the permissions it needs.

In every example below, replace https://demo.viggo.vet, https://demo-api.viggo.vet, the email and the password with your own values.

Claude Code

One command

claude mcp add --transport http viggo https://mcp.viggo.vet/mcp \
  --header "X-Viggo-Clinic-Url: https://demo.viggo.vet" \
  --header "X-Viggo-Api-Url: https://demo-api.viggo.vet" \
  --header "X-Viggo-Email: ai-assistant@yourclinic.com" \
  --header "X-Viggo-Password: YOUR_PASSWORD"

Or a project `.mcp.json`

Keeps the password out of the file — set VIGGO_EMAIL and VIGGO_PASSWORD in your shell environment.

{
  "mcpServers": {
    "viggo": {
      "type": "http",
      "url": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic-Url": "https://demo.viggo.vet",
        "X-Viggo-Api-Url": "https://demo-api.viggo.vet",
        "X-Viggo-Email": "${VIGGO_EMAIL}",
        "X-Viggo-Password": "${VIGGO_PASSWORD}"
      }
    }
  }
}

Claude Desktop

Settings → Developer → Edit Config (claude_desktop_config.json). Requires Node.js 18+. Restart Claude Desktop afterwards.

{
  "mcpServers": {
    "viggo": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.viggo.vet/mcp",
        "--header", "X-Viggo-Clinic-Url:${VIGGO_CLINIC_URL}",
        "--header", "X-Viggo-Api-Url:${VIGGO_API_URL}",
        "--header", "X-Viggo-Email:${VIGGO_EMAIL}",
        "--header", "X-Viggo-Password:${VIGGO_PASSWORD}"
      ],
      "env": {
        "VIGGO_CLINIC_URL": "https://demo.viggo.vet",
        "VIGGO_API_URL": "https://demo-api.viggo.vet",
        "VIGGO_EMAIL": "ai-assistant@yourclinic.com",
        "VIGGO_PASSWORD": "YOUR_PASSWORD"
      }
    }
  }
}

Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project)

{
  "mcpServers": {
    "viggo": {
      "url": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic-Url": "https://demo.viggo.vet",
        "X-Viggo-Api-Url": "https://demo-api.viggo.vet",
        "X-Viggo-Email": "ai-assistant@yourclinic.com",
        "X-Viggo-Password": "YOUR_PASSWORD"
      }
    }
  }
}

VS Code (GitHub Copilot agent mode)

.vscode/mcp.json — VS Code asks for the password once and stores it securely.

{
  "inputs": [
    { "type": "promptString", "id": "viggo-password", "description": "viggoVet password", "password": true }
  ],
  "servers": {
    "viggo": {
      "type": "http",
      "url": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic-Url": "https://demo.viggo.vet",
        "X-Viggo-Api-Url": "https://demo-api.viggo.vet",
        "X-Viggo-Email": "ai-assistant@yourclinic.com",
        "X-Viggo-Password": "${input:viggo-password}"
      }
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "viggo": {
      "serverUrl": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic-Url": "https://demo.viggo.vet",
        "X-Viggo-Api-Url": "https://demo-api.viggo.vet",
        "X-Viggo-Email": "ai-assistant@yourclinic.com",
        "X-Viggo-Password": "YOUR_PASSWORD"
      }
    }
  }
}

Any other MCP-compatible agent

Add a remote / Streamable HTTP MCP server with:

Setting	Value
Name	`viggo`
URL	`https://mcp.viggo.vet/mcp`
Headers	`X-Viggo-Clinic-Url`, `X-Viggo-Api-Url`, `X-Viggo-Email`, `X-Viggo-Password` (as above)

Most agents accept this generic JSON. If yours only supports local (stdio) servers, use the npx mcp-remote form shown for Claude Desktop.

{
  "mcpServers": {
    "viggo": {
      "url": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic-Url": "https://demo.viggo.vet",
        "X-Viggo-Api-Url": "https://demo-api.viggo.vet",
        "X-Viggo-Email": "ai-assistant@yourclinic.com",
        "X-Viggo-Password": "YOUR_PASSWORD"
      }
    }
  }
}

Try it

After connecting, ask your agent:

"Using viggo, who am I and what can I access?"
"List today's appointments from viggo."
"Search viggo for a patient named Bella and summarise her medical history."
"Show this month's end-of-day totals and outstanding invoices."

Good to know

Gentle on your clinic's system. Requests are paced (about one per second per user, one at a time) so the viggoVet app stays fast for your team. Big questions can take a little longer — that's expected.
Read-focused. The built-in tools only read data. Your viggoVet permissions still apply to everything.
Keep credentials private. Don't commit config files that contain passwords to a code repository; prefer environment variables or your agent's secret prompts.
Encrypted. Always connect over https://.

Coming soon: API tokens

We're adding API tokens to replace email/password. When they're ready, the switch is painless and optional:

Both methods work at the same time — no forced cut-over, no downtime.
To switch, replace the X-Viggo-Email + X-Viggo-Password headers with a single X-Viggo-Token header.
You do not reinstall anything — the endpoint is unchanged.
Tokens don't use up your one web session, so they're ideal for 24/7 agents.