Skip to content

How do you handle upstream MCP servers changing schema/tool list under MCP-Bridge? #126

Description

@anythingoah

Hey, not a bug report more of a question about how MCP-Bridge handles a specific case.

If one of the MCP servers you're bridging to changes its tool list or schema (renamed tool, changed param, dropped a field) while MCP-Bridge is running against it, how does that usually surface? Does it error out at request time, does the OpenAI-compatible endpoint just silently pass through whatever the new shape is, or is there something that catches it before a client hits it?

Curious whether this has come up in practice with any of the servers you bridge to, or if it's not really been an issue.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions