Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix HTTP-based MCP server tools not available to model despite showing "Running" status [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56186•Fetched 2026-05-06 06:34:54
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
sjlacertesjlacerte
Participants
github-actions[bot]github-actions[bot]localdenlocaldensjlacertesjlacerte
Timeline (top)
labeled ×4commented ×2closed ×1

When an MCP server is configured with "type": "http" (Streamable HTTP transport), the Claude Code UI shows the server as "Running" with the correct tool and prompt count, but those tools are not injected into the model's context and cannot be called.

Root Cause

When an MCP server is configured with "type": "http" (Streamable HTTP transport), the Claude Code UI shows the server as "Running" with the correct tool and prompt count, but those tools are not injected into the model's context and cannot be called.

Code Example

{
      "mcpServers": {
        "cloudflare-docs": {
          "type": "http",
          "url": "https://docs.mcp.cloudflare.com/mcp"
        }
      }
    }
RAW_BUFFERClick to expand / collapse

Description

When an MCP server is configured with "type": "http" (Streamable HTTP transport), the Claude Code UI shows the server as "Running" with the correct tool and prompt count, but those tools are not injected into the model's context and cannot be called.

Steps to Reproduce

  1. Add a remote HTTP MCP server to .mcp.json: 
    {
  "mcpServers": {
    "cloudflare-docs": {
      "type": "http",
      "url": "https://docs.mcp.cloudflare.com/mcp"
    }
  }
}
  2. Open the /mcp panel and click "Start" on the server
  3. Verify the UI shows Running | 2 tools | 1 prompts
  4. Ask Claude to use one of the server's tools (or use ToolSearch to look for them)

Expected Behavior

The server's tools are available to the model and can be invoked.

Actual Behavior

Tools are not available to the model. ToolSearch returns no results for the server's tools. The model falls back to training knowledge instead of querying the MCP server.

Environment

  • Platform: macOS 23.6.0
  • Claude Code version: (check with claude --version)
  • Transport type: http (Streamable HTTP — also reproduced with "type": "sse" prior to switching)

Additional Context

Stdio-based MCP servers in the same .mcp.json do not exhibit this issue. The problem appears specific to remote HTTP transport servers.

extent analysis

TL;DR

The issue may be resolved by verifying the configuration of the HTTP MCP server in .mcp.json and ensuring that the server is correctly exposing its tools.

Guidance

  • Review the .mcp.json configuration to ensure that the url field for the HTTP MCP server is correctly formatted and points to the expected endpoint.
  • Verify that the server is correctly configured to expose its tools over the HTTP transport, potentially by checking server logs or documentation.
  • Test the server's tools using a tool like curl or a web browser to ensure they are accessible and functioning as expected.
  • Consider comparing the configuration and behavior of the HTTP MCP server with a working Stdio-based MCP server to identify potential differences.

Example

No code snippet is provided as the issue appears to be related to configuration rather than code.

Notes

The issue seems specific to remote HTTP transport servers, and the problem may be related to the server's configuration or the client's ability to connect to it. Further investigation into the server's documentation and configuration may be necessary to resolve the issue.

Recommendation

Apply workaround: Verify and adjust the server configuration to ensure that tools are correctly exposed over the HTTP transport, as the issue appears to be related to the server's configuration rather than a version-specific problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix HTTP-based MCP server tools not available to model despite showing "Running" status [2 comments, 3 participants]