Metabase MCP

[j-bucks]

MCP server URL or name

https://metabase.fusionauth.co/api/mcp

How are you connecting to this server?

From a custom connector URL I entered manually

Where does the issue occur?

When pressing the Connect button

When did you last reproduce this?

2026-04-23 10:43 Central time

Browser and OS

Chrome, MacOS

Describe the issue

The flow ID: ofid_44dbfe2ed0dcb2e9
Your MCP URL: https://metabase.fusionauth.co/api/mcp
That it works in other MCP clients: Opencode, Claude Code
That it's a self-hosted Metabase v0.60 using the native MCP server with OAuth 2.0 and Streamable HTTP transport

Error details

Couldn't reach the MCP server. You can check the server URL and verify the server is running. If this persists, share this reference with support: "ofid_d32594c73257a651"


https://claude.ai/desktop/connected/settings/connectors?&server=963e39c1-5b22-4375-ae64-9622ff57e5f7&step=start_error&flow_id=ofid_d32594c73257a651

Expected behavior

When connect should launch OAuth window to connect.

T

Additional context

[stevegoulet]

I am having similar issues connecting to the Metabase MCP using Claude.ai and desktop - mine fails at authorization. The same Metabase MCP works just fine in Claude Code. Did you try yours with CC?

Claude thinks that my problem is related to a MCP bug as noted in these existing issues:
#184
#171

[j-bucks]

I am having similar issues connecting to the Metabase MCP using Claude.ai and desktop - mine fails at authorization. The same Metabase MCP works just fine in Claude Code. Did you try yours with CC?

Claude thinks that my problem is related to a MCP bug as noted in these existing issues: #184 #171

Yep @stevegoulet -- CC and other MCP clients its works just fine. The problem is I'm trying to launch this as a custom connector for an organization which is where its frustrating.

[localden]

Thanks for the detailed report. We've investigated and found the cause.

When claude.ai attempts to connect to metabase.fusionauth.co, the hostname resolves to private IP addresses (in the 10.0.0.0/8 range). claude.ai's connectors run on Anthropic's infrastructure and reach your MCP server over the public internet, so servers on private/internal networks aren't reachable. As a security measure, connections to private IP ranges are blocked before any request is attempted — which is why you see "Couldn't reach the MCP server" immediately at the start of the auth flow.

This works in the Claude Code CLI because the CLI connects directly from your local machine, which is presumably on the same network as your Metabase instance.

To use this server with claude.ai connectors, the MCP endpoint needs to be reachable from the public internet. Options:

1. Expose the MCP endpoint on a public IP (with appropriate auth — OAuth, which your server already advertises, is fine).
2. Use a tunneling solution (e.g., Cloudflare Tunnel, ngrok) to give the endpoint a public address.

Closing as working-as-intended on our side, but happy to help if you hit issues after making the endpoint public.