← Back to Blog

2026-09-22 • 5 min read • Fix

How to Fix an MCP Server That Isn't Showing Up in Claude

How to find a missing Claude connector by checking the MCP Studio URL, the per-chat toggle, who can add connectors, and the Free plan limit.

Claude answers whether or not your server is in the conversation. A missing connector looks like a normal reply, which is why it takes a minute to notice the server never ran.

Two different things get called "not showing up." The connector is absent from the list, or it is in the list and this chat is not using it. The second one is more common.

What "showing up" means

The connector's name is in Claude's connector list, and the toggle is on for this chat. You then see connector activity beside the reply. No activity means Claude wrote the answer without calling you.

The dialog, with screenshots, is Create a Claude custom connector. Plan limits are in Anthropic's custom connector guide. A Free plan holds one custom connector.

Why the toggle is the usual miss

The connector can exist on the account and stay off in the chat. You added it last week. This conversation never turned it on.

The URL can be the wizard. That address will save and never connect. The field wants the URL that contains /api/mcp/ and the server name.

An Owner has to add it first on Team and Enterprise. If you cannot see Add custom connector, that is the reason. After an Owner adds it, everyone else clicks Connect.

Use the URL from MCP Studio

MCP Studio is the no-code builder on Appa Tools. Open the server's setup page and copy the URL. If you still need the server, build it in the wizard. The docs version is Give Claude access to your documentation.

  1. Open Claude. Click +, then Connectors.
  2. If the name is missing, click Add connector, then Add custom connector.
  3. Paste the MCP Studio URL, not the wizard page and not the dashboard.

Claude's Add custom connector dialog, with fields for Name and MCP server URL

  1. Back in the chat, open Connectors and turn this one on.
  2. For a private server, add the access token in the connector settings. Curl with the bearer token tells you whether the token is the problem before you keep clicking. The header is in the private servers guide.

A Free plan already holding one connector will not take a second. Remove the other one or pick a different Claude plan. That limit is Claude's, not the server's.

Claude Desktop can also be configured with a local command instead of a custom connector. That mcp-remote JSON is in the private servers guide. It is a different setup from the connector list.

Check that it works

Ask a question you know is in the source. Look for connector activity beside the reply. The citation should be your page.

Indexing does not have to finish for the connector to appear. It has to finish before you judge the answers.

If it is still missing

Change one thing. Confirm the URL with curl before you delete the connector and add it again. That check is Fix an MCP server that isn't connecting. If the connector is on and the answer is still wrong, the order is Debug an MCP server.

Turn the connector on today

Open MCP Studio, copy the /api/mcp/ URL, and paste it into Claude as a custom connector. Turn the toggle on for this chat and ask one question you can check. Connector activity beside the reply means it is in the conversation.

Where to go next