Skip to content

Cannot save existing MCP server config while duplicate config can be created #9798

@peicodes

Description

@peicodes

Slack feedback: Can't save an MCP server config, but can create a new one with the exact same config JSON. Is it related to secrets? Kinda confusing why and what I can do about it, or if it's a bug.

Slack message: https://warpdev.slack.com/archives/C08KTPNQN65/p1774610414964769

Requested follow-up:

  • Reproduce editing/saving an existing MCP config vs creating a new one with identical JSON
  • Verify whether secret handling/redaction causes save to fail
  • Improve UX/error messaging so users understand why save failed and how to recover

Linear: APP-3657

Metadata

Metadata

Assignees

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

Relationships

None yet

Development

No branches or pull requests

Issue actions