[BUG] MCP HTTP server resources not accessible via ListMcpResourcesTool and ReadMcpResourceTool

Resolved 💬 3 comments Opened Nov 9, 2025 by mattyellen Closed Jan 12, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code's MCP integration tools fail to list or read resources from HTTP-based MCP servers, even though the servers are responding correctly to MCP protocol requests.

What Should Happen?

  • ListMcpResourcesTool should return a list of available resources
  • ReadMcpResourceTool should successfully read resource content

Error Messages/Logs

Steps to Reproduce

  1. Set up an HTTP-based MCP server that exposes resources
  2. Configure the server in .mcp.json with type "http"
  3. Start the server and verify it's responding to HTTP requests
  4. Try using ListMcpResourcesTool or ReadMcpResourceTool in Claude Code

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.36

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Actual Behavior

  • ListMcpResourcesTool returns empty array []
  • ReadMcpResourceTool returns error: "Not connected"

## Verification

Direct curl requests to the same server successfully return resources:

```bash
# List resources - WORKS
curl -s -X POST http://127.0.0.1:8000/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"resources/list"}'

# Returns: {"jsonrpc":"2.0","id":1,"result":{"resources":[...]}}

# Read resource - WORKS
curl -s -X POST http://127.0.0.1:8000/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"resources/read","params":{"uri":"<resource-uri>"}}'

# Returns resource content successfully

##  Additional Context

  Tools from the same HTTP MCP server work correctly - the issue appears isolated to resource operations. Example .mcp.json configuration:

{
"mcpServers": {
"my-server": {
"type": "http",
"url": "http://127.0.0.1:8000/mcp"
}
}
}```

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗