Repository navigation
A public record of gitlab-mcp's tool definitions over time #719
GautamTalksDev
started this conversation in
General
Replies: 1 comment
|
Follow-up: here's a 35-second walkthrough of what this looks like when it fires, including a real change it caught on day one. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I've been building a public log of MCP tool definitions, because clients ask a user to approve a server once and then never re-check. If a description changes in a later release, nothing tells that user.
Here's the page for gitlab-mcp: https://mcp-pin.gautamkhosla.com/servers/4914d06c4a8c19cf.html
117 tools and 58,121 characters of description. bulk_publish_draft_notes and update_project are both write operations against someone's GitLab, and their descriptions are what the model reads when deciding whether to call them. A change there after approval is a behaviour change nobody sees.
All 117 are fingerprinted now, so any future change shows up as a dated diff. If it's useful, there's a badge:
No ask beyond that. If you'd rather not be crawled, say so and it stops, no explanation needed: https://mcp-pin.gautamkhosla.com/about.html
And if this is useless to you, telling me why would be the most helpful reply I could get.
Gautam
All reactions