[BUG] /mcp UI shows "Auth: not authenticated" for HTTP MCP servers using Bearer token headers

Resolved 💬 4 comments Opened Jan 9, 2026 by zain534102 Closed Feb 23, 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?

The /mcp UI displays Auth: ✗ not authenticated for HTTP MCP servers configured with Bearer token authentication in headers, even though the authentication is working correctly. All tools load successfully and authenticated requests succeed, but the UI incorrectly indicates an authentication failure. This creates user confusion as the red "x" suggests a problem when none exists.

What Should Happen?

When a Bearer token is configured in the headers section of an HTTP MCP server config, the UI should recognize this as a valid authentication method and display Auth: ✓ authenticated or Auth: ✓ Bearer token (header). The auth status indicator should accurately reflect that authentication credentials are configured and working, not just OAuth-style authentication flows.

Error Messages/Logs

No error messages or logs - this is a UI display issue, not a functional error.

  The /mcp status display shows:
  Project-manager MCP Server
  Status: ✓ connected
  Auth: ✗ not authenticated
  URL: https://pm.avrillord.co.uk/mcp
  Config location: /Users/zainali/.claude.json
  Capabilities: tools
  Tools: 15 tools

  Despite Auth: ✗ not authenticated, all 15 tools load and function correctly with authenticated requests succeeding.
/Users/zainali/Downloads/image (3).png

Steps to Reproduce

  1. Add an HTTP MCP server with Bearer token auth to ~/.claude.json:
  {
    "mcpServers": {
      "my-server": {
        "type": "http",
        "url": "https://your-mcp-server.com/mcp",
        "headers": {
          "Authorization": "Bearer your-api-token-here"
        }
      }
    }
  }
  1. Start a new Claude Code session:

claude

  1. Run the /mcp command
  2. Select the configured MCP server from the list
  3. Observe the status display - note that Auth: ✗ not authenticated is shown
  4. Select "View tools" - confirm all tools are loaded
  5. Use any tool from the MCP server - confirm it works with authentication

Result: Auth shows as failed (✗) but everything actually works correctly.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.2

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

<img width="1663" height="277" alt="Image" src="https://github.com/user-attachments/assets/d97ed724-b261-424b-8380-f428dd17e372" />

View original on GitHub ↗

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