Troubleshooting

Connection issues

Claude Desktop says "Could not connect"

Confirm the URL is https://mcp.vacationtracker.io/mcp (with the trailing /mcp, not just the domain root). Hitting the root in a browser is fine and serves a landing page, but that isn't the MCP endpoint.
Check your firewall allows outbound HTTPS to mcp.vacationtracker.io and auth.vacationtracker.io.
If your organization uses a proxy with SSL inspection, MCP clients usually fail the TLS handshake. Add both domains to the proxy's bypass list.

Your MCP client must support:

RFC 9728 protected resource metadata discovery,
RFC 8414 authorization server metadata discovery,
RFC 7591 Dynamic Client Registration, and
PKCE (S256) on the authorization code flow.

All mainstream clients (Claude Desktop, Claude Code, Cursor) support these. Older or custom clients that require a pre-registered client ID won't work. The server doesn't issue static client credentials for MCP.

"Invalid token" / 401 after authorizing

The Bearer token carries your scopes on the custom:grantedScopes claim. If you see repeated 401s after a successful OAuth flow:

Disconnect the Vacation Tracker connector in your AI client's settings.
Reconnect and watch the consent screen. Make sure you grant the scopes the tool needs (see Scopes).
If the problem persists, contact developers@vacationtracker.io with the error message from your client's logs.

Tool-call errors

Every error the server returns is a standard JSON-RPC 2.0 error with a support block in error.data:

{
  "support": {
    "email": "developers@vacationtracker.io",
    "feedback_url": "https://www.votito.com/public/ideabank/...",
    "error_tracked": true,
    "note": "This error has been automatically logged. …"
  }
}

The error_tracked: true flag is literal. Every error path emits an MCP_TOOL_ERRORED event and a structured CloudWatch log with a request ID. The developer team can trace an incident by that request ID without any extra context from you.

`-32601 Method not found`

The client requested a JSON-RPC method the server does not implement. In practice this only happens if a client is on a newer MCP protocol version than the server supports. File an issue at developers@vacationtracker.io.

`-32602 Invalid params`

The arguments to a tool did not match its input schema. Most commonly:

Unknown tool name: a client called tools/call with a name the server does not expose.
Ambiguous name reference: e.g. passing department: "Eng" when both "Engineering" and "Engineering Leads" match. The error's data block lists the candidate IDs so the LLM can retry with a specific one.

`-32001 Missing required scope`

The Bearer token did not include the scope a tool requires. Example: calling find_users with only mcp:workspace:read. Reconnect and grant the missing scope on the consent screen.

`-32603 Internal error`

An unexpected server-side failure. The error message is surfaced to the client, and the full stack trace is captured in CloudWatch. When reporting, include:

the tool name and approximate timestamp,
the JSON-RPC id if visible,
any error.message text your client shows.

Feature requests

MCP is intentionally read-only today. If you need a tool that doesn't exist yet (say get_user_balance, write operations, or balance reporting), submit via the feedback_url in the support block, or email developers@vacationtracker.io directly.

Troubleshooting

On this page