MCP · beta

Connect your AI agent to viggoVet

The viggoVet MCP server lets any AI assistant securely read your clinic's data — patients, clients, calendar, invoices, inventory and more — over the Model Context Protocol.

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

What you need

Header	Value	Required
`X-Viggo-Clinic`	your clinic subdomain (e.g. `myclinic` from `myclinic.viggo.vet`)	Yes
`X-Viggo-Token`	API token (coming soon — preferred)	— or —
`X-Viggo-Email`	your viggoVet login email	today
`X-Viggo-Password`	your viggoVet password	today

Send X-Viggo-Clinic plus either a token or email + password. Your viggoVet permissions are enforced on every call — the agent can never exceed what your account is allowed to do.

One session per user. viggoVet currently allows one active session per user. If you connect with your normal email/password, you'll be logged out of your viggoVet web session while the agent is active. For always-on agents, ask your viggoVet admin for a dedicated AI user (or wait for API tokens — below).

Connect — Claude Code

claude mcp add --transport http viggo https://mcp.viggo.vet/mcp \
  --header "X-Viggo-Clinic: YOUR_CLINIC" \
  --header "X-Viggo-Email: you@yourclinic.com" \
  --header "X-Viggo-Password: YOUR_PASSWORD"

Connect — Claude Desktop / Cursor (mcp.json)

{
  "mcpServers": {
    "viggo": {
      "transport": "http",
      "url": "https://mcp.viggo.vet/mcp",
      "headers": {
        "X-Viggo-Clinic": "YOUR_CLINIC",
        "X-Viggo-Email": "you@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 patients named Bella."

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, change one line: replace the X-Viggo-Email + X-Viggo-Password headers with a single X-Viggo-Token header.
You do not reinstall or update anything — the endpoint is unchanged.
Tokens don't consume your one web session, so they're ideal for 24/7 agents.