Skip to content

Surface better errors when MCP configs fail to unmarshal #9807

Open
Open
Surface better errors when MCP configs fail to unmarshal#9807
Labels
area:mcpMCP server integrations, tool connections, and resource providers.bugSomething isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.warp:prioritizedIssues prioritized by the Warp team.
@peicodes

Description

@peicodes
peicodes
opened on May 1, 2026

Instructions for Warp Agent: Perform an investigation only, unless instructed otherwise. When investigating, do not take external actions like making Github comments or opening pull requests.

aloke said:

I had an MCP server that wasn't starting and I could not figure out why.

Ended up spending a ton of time debugging and turns out we require (?) an empty args field in each MCP definition for it to be valid. I've seen at least a few different MCP configs that omit args (see second screenshot) and it seems like an unnecessary requirement.

Also separately, this just silently failed for me. We need better error messaging, I was only able to debug by actually getting agent mode to add debug logs to warp.

image.png

image.png

Linear: APP-3075

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mcpMCP server integrations, tool connections, and resource providers.bugSomething isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.warp:prioritizedIssues prioritized by the Warp team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions