Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Invalid MCP Server Configuration in .mcp.json: Schema Validation Failed [1 comments, 2 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#56254•Fetched 2026-05-06 06:33:04
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
habakuk007habakuk007
Participants
github-actions[bot]github-actions[bot]habakuk007habakuk007
Timeline (top)
labeled ×3commented ×1

Error Message

The mcp server that is configured in .mcp.json is not found. /doctor shows an error: └ [Error] mcpServers: Does not adhere to MCP server configuration schema

RAW_BUFFERClick to expand / collapse

Bug Description The mcp server that is configured in .mcp.json is not found. /doctor shows an error:

[Failed to parse] Project config (shared via .mcp.json) Location: C:\Users\Stefan\Documents\Sourcecode\produktiv\t3-requirements.mcp.json └ [Error] mcpServers: Does not adhere to MCP server configuration schema

.mcp.json

{
  "mcpServers": {
    "atlassian": {
      "type": "http",
      "url": "https://mcp.atlassian.com/v1/mcp/authv2"
    }
  }
}

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.128
  • Feedback ID: aa44d47e-c620-4fc0-a82f-6418def8d5f3

extent analysis

TL;DR

The issue is likely due to an invalid MCP server configuration in the .mcp.json file, and verifying the schema adherence is the first step to resolve it.

Guidance

  • Check the MCP server configuration schema to ensure that the provided configuration in .mcp.json adheres to it, focusing on the mcpServers section.
  • Verify that the type and url fields in the atlassian configuration are correctly formatted and valid according to the schema.
  • Review the error message from /doctor for any specific hints about what part of the configuration is not adhering to the schema.
  • Consider consulting the documentation for the expected format of the mcpServers configuration in .mcp.json to identify any potential mismatches.

Notes

The provided information does not include the exact schema for MCP server configuration, which is necessary for a precise fix. The solution will depend on ensuring that the .mcp.json file's content matches the required schema.

Recommendation

Apply workaround: Adjust the .mcp.json configuration to match the MCP server configuration schema, as indicated by the error message and supported by consulting the relevant documentation.

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…
#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING