Repository navigation
A public record of n8n-mcp's tool definitions over time #1055
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 Romuald,
I've been building a public log of MCP tool definitions, because clients ask you to approve a server once and then never re-check. If a description changes afterwards, nothing tells the user.
Here's the page for n8n-mcp: https://mcp-pin.gautamkhosla.com/servers/2b32a780ae836f7c.html
Yours stood out while I was looking through it. get_node's description is doing real work rather than just labelling. The token budgets and mode switches are an operational contract with the model, so a change there is a behaviour change, not a docs change.
You've also shipped 273 releases, so these descriptions genuinely move. That's the interesting case: someone approved a version of get_node months ago and their client has never re-checked since.
All 7 tools are fingerprinted and the history starts today. If it's useful, there's a badge showing users the definitions haven't moved:
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