An organization rollout publishes the Tindre MCP server entry through the AI client’s administrative controls. It must not distribute a shared Tindre credential. Every member authenticates as themselves and receives their own filtered capability catalog.
- 1
Set Tindre policy
In Administration → Security, decide whether API and MCP are allowed and whether they are read-only.
- 2
Approve data handling
Review the client provider, agreement, and connected-AI disclosure.
- 3
Publish the server entry
Use the AI workspace’s connector or managed MCP configuration.
- 4
Pilot with representative roles
Test ordinary employees, builders, and restricted readers before broad enablement.
Policy is a ceiling
Organization settings can turn API/MCP off or force every credential to read-only. The cap applies to administrators too and never grants access the person lacks.
Give clients a short usage instruction
Tell the client when to reach for Tindre and require it to say when no governing Standard exists.
Expect different catalogs
Two members can see different tools and results. This is correct when their access roles or Role visibility differ.
Monitor the shared endpoint
The MCP endpoint limits requests per person and organization, including concurrent calls. A wide rollout can meet the organization ceiling before individual users do; handle typed rate responses rather than retrying aggressively.