feat: per-client server and tool access, and tool counts on my servers #45
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/client-tool-access"
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 choose which servers and tools each connected client and MCP key can use. Everything is allowed until switched off, and the switches only narrow what the user can already reach.
Blocks live in
client_hidden_serversandclient_hidden_tools. Each row belongs to one OAuth client (per user) or one MCP key. OAuth rows are not keyed by grant, because a password change revokes every grant and the client would sign in again with its restrictions gone.Evidence
After:
nix develop -c ./scripts/ci.shexits 0: lint, typecheck, build, audit, and API 331, web 153, runner 46 and shared 5 tests passing.Also checked in the running app with sample data, at 1280 px and 390 px wide, with no sideways scrolling.
Merge Danger
Door: two-way
Migration
0007_client_accessonly adds two tables. Rolling back removes the switches, so clients regain everything their user can reach.Blast Radius: gateway
Every
tools/list,tools/callandmcphub__statuson/mcpnow reads the block tables. A client that registers again through dynamic registration gets a new client id and starts with nothing blocked. A per-user server's tools can be switched individually only after an admin runs Test, as on its server page today.trail checkflagsschema.tsandportal/servers.tsagainst two learnings. Both are false matches: no admin tool is added to/mcp, and catalog deletion and the missing-tool-is-enabled rule are unchanged.🤖 Generated with Claude Code