Connecting an AI Assistant#

GekkoVet’s MCP server can be connected to any MCP-compatible client. The endpoint and transport are the same for all of them:

• URL: https://mcp.gekkovet.workers.dev/mcp
• Transport: Streamable-HTTP (recommended) or SSE at /sse
• Auth: OAuth 2.0 — handled interactively on first connect

Below are setup instructions for the most common clients.

Claude Desktop#

Claude Desktop currently speaks MCP over local stdio only, so a small bridge is needed to connect it to the remote GekkoVet server. Use mcp-remote:

1. Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

2. Add a gekkovet entry under mcpServers:

   {
     "mcpServers": {
       "gekkovet": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://mcp.gekkovet.workers.dev/mcp"
         ]
       }
     }
   }

3. Restart Claude Desktop. The first time the bridge connects, a browser window will open asking you to sign in to GekkoVet. After authenticating, Claude will have access to all GekkoVet tools.

If you already have other MCP servers configured, just add `gekkovet` as an additional entry alongside them — don't replace the whole `mcpServers` block.

ChatGPT and other native MCP clients#

Clients that speak remote MCP natively (for example, ChatGPT’s custom MCP connectors) can connect directly without a bridge:

• Server URL: https://mcp.gekkovet.workers.dev/mcp
• Transport: Streamable-HTTP
• Authentication: OAuth 2.0 — let the client handle the flow; it will redirect you to the GekkoVet login page

Each client’s UI differs. Look for “Add MCP server”, “Custom connector”, or equivalent, and provide the URL above.

MCP Inspector#

For testing and exploring the available tools interactively, use the official MCP Inspector:

npx @modelcontextprotocol/inspector

In the inspector UI:

1. Set Transport Type to Streamable HTTP.
2. Set Server URL to https://mcp.gekkovet.workers.dev/mcp.
3. Click Quick OAuth Flow to authenticate with your GekkoVet account.
4. Click Connect, then List Tools — you should see all 20 GekkoVet tools.
5. Invoke any tool and inspect the response. The whoami tool is useful to confirm your identity is propagating correctly.

Verifying the server is reachable#

The OAuth discovery endpoint is public and doesn’t require authentication — use it to confirm connectivity:

curl https://mcp.gekkovet.workers.dev/.well-known/oauth-authorization-server

You should get back a JSON document listing the authorization, token, and registration endpoints.

A bare request to /mcp without a token will return 401 with an OAuth challenge — that’s expected:

curl https://mcp.gekkovet.workers.dev/mcp
# {"error":"invalid_token","error_description":"Missing or invalid access token"}