Skip to content

Detect duplicate and conflicting MCP definitions #2

Description

@NoureddinBakir

Problem

The same MCP server can appear in global configuration, project configuration, or both tools. The current manifest preserves entries but does not explain duplicates or conflicts.

Proposed direction

Normalize MCP identities and produce a conflict report showing where definitions overlap without choosing or activating a winner.

Acceptance criteria

  • Identifies exact duplicates separately from conflicting definitions.
  • Preserves Claude Code or Codex source and global or project scope.
  • Never compares or emits secret values.
  • Treats redacted arguments and environment variable names conservatively.
  • Does not silently merge, delete, or activate a server.
  • Adds fixtures covering URL, stdio, environment-key, and cross-scope conflicts.
  • Documents the conflict model in the README.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions