Skip to content

Fine-grained tool versioning #594

Description

@keysersoft

Editing a tool definition changes it for every client on the next request. That is the right default, and it is also how a working agent breaks silently when someone renames a parameter.

Scope

  • Tool definitions get a version; edits create a new one rather than overwriting.
  • An MCP server can pin a tool to a version.
  • A diff view in the editor showing what changed between versions.
  • Rollback.

Open question: does this belong per tool, or is a per-server snapshot ("this server serves the tool set as of X") both simpler and more useful? Say so in the comments.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    roadmapOn the published roadmap; exempt from the stale bot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions