Repository navigation
Member visibility: Restricted mode, complete
- A member who is not an admin sees only the MCP servers they own, everywhere: servers page and API, server picker and consent page, connections, API keys, audit and tool performance, and the server links of the shared endpoint. Other servers answer 404, like unknown ids.
- File Search detail is shown only to the connector's owner and to admins.
- Knowledge graph, skills, learning projects and plan fit are admin-only when the workspace is restricted.
- Testing values against a connector's stored credentials (
POST /api/adapters/:slug/verifywithconnectorId) needs the connector's owner or an admin, in every workspace. - Every API route now has a recorded visibility decision, and an automated test fails when a route has none. A database test checks a restricted Viewer end to end.
Roles page shows every role
- Settings → Roles and Users list every MCP role of each member, where it comes from (set by an admin, a single sign-on group, or all workspaces) and the connectors those roles reach. Before, the page showed one role per member, so a role from a sign-on group could widen access unseen.
- Manual roles are edited with a multi-select. New admin endpoint
GET /api/roles/members.
Secrets in connector base URLs
- Webhook tokens typed into a base URL (Bitrix24, Slack, Discord, Microsoft Teams, Zapier, Make) and passwords in
user:password@are moved into encrypted variables when a connector is saved. The base URL keeps the host and shows{{VARIABLE}}where the secret was; calls work as before.
After upgrading
- At start-up, the server moves such secrets out of existing connectors and logs one summary line. Nobody has to open or save connectors.
- In a restricted workspace, members no longer see other members' MCP servers.
No database migration.