Connecting a client

The Bucketlist MCP server runs at:

https://mcp.bucketlisttravel.app

It speaks the standard MCP protocol over HTTP, with OAuth 2.0 for authentication. You'll authorize each client once — after that, it can act on your behalf until you revoke it from the Account page.

Claude Desktop

In Claude Desktop, open Settings → Connectors → Add custom connector and enter:

• Name: Bucketlist
• URL: https://mcp.bucketlisttravel.app

Claude will open a browser tab to go.bucketlisttravel.app, where you'll log in (if you aren't already) and approve access. Once you approve, the connector is live in Claude Desktop and you can ask it to plan trips.

Generic MCP client

If your client supports remote MCP servers with OAuth, point it at:

{
  "mcpServers": {
    "bucketlist": {
      "url": "https://mcp.bucketlisttravel.app",
      "transport": "http"
    }
  }
}

The server advertises its OAuth metadata at:

https://mcp.bucketlisttravel.app/.well-known/oauth-protected-resource

A standards-compliant client will discover the authorization server from there and walk you through the consent flow.

What gets shared

When you authorize a client, you grant it the same access you have — no more, no less. Specifically:

• Read and write all trips you own or collaborate on.
• Read and write all vision boards you own or collaborate on.
• Read community places, place stats, and users' ranked lists.
• Cannot read or change your billing, password, or other account settings.

Revoking access

Open go.bucketlisttravel.app/account, scroll to Connected MCP clients, and click Revoke next to any client. The token is invalidated immediately; the next request from that client will fail with a 401.

Troubleshooting