feat: let users hide single tools from their own /mcp #22
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/user-tool-visibility"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Users can switch off single tools for their own
/mcp, so the tools they don't use stop taking up their agent's context. Descriptions also lose their[Server Name]prefix.Migration:
0004_user_hidden_tools.sql(new table, PK user + server + tool name, cascades on user and server delete).Evidence
alpha__echodescription was"[Alpha] Echo the text back".After:
gateway.test.ts: alice hidesalpha__fail-> getstools/list_changed, it's gone from her list, calling it throwsUnknown tool, bob still sees it, unhiding brings it back. Description is"Echo the text back".portal.test.ts: hide is per user, idempotent, 404 for an unknown tool and for a user without access.ServerPage.test.tsx: the switch sends{ hidden: true }and the header reads1 of 2 tools in your MCP.npm test: all four workspaces pass (288 + 109 + 46 + 5). Lint and typecheck are clean.trail checkflagsuser_hidden_toolsagainst the learning that ruled out admin tools on the user/mcp. That's a lexical match: this adds no tools to/mcp, it only filters them per user.Merge Danger
Door: two-way
The migration only adds a table. Rolling back leaves an unused table behind and drops users' tool choices.
Blast Radius: small
Connected agents see shorter descriptions on every tool, so clients that pinned on the old text would notice. Tools that only exist in a per-user process (catalog empty until an admin runs Test) can't be hidden yet.
🤖 Generated with Claude Code