MCP enterprise administration
Use this guide with the connection settings and your chosen host guide. Confirm availability and enabled capabilities for your organization with Uhuu before configuration.
Responsibilities
| Owner | Responsibilities |
|---|---|
| Customer host administrator | Host licenses, tenant/environment policies, approved users, connector or agent distribution, and host-held credentials |
| Uhuu team administrator and template owner | Team membership and roles, template access, published contracts, approved source data, and document review |
| Uhuu support | Supported connection settings, enabled capabilities, and incident handling |
| Customer security/privacy reviewer | Accepted data classifications, provider processing terms, retention, public-link exposure, and offboarding requirements |
Authentication and least privilege
Uhuu uses OAuth authorization code flow with S256 PKCE. An unauthenticated MCP request returns a challenge identifying protected-resource metadata; the host discovers the authorization server and directs the user through Uhuu sign-in and team consent. The gateway verifies signed tokens against the issuer's public keys and the exact resource audience.
Use the OAuth client and callback configuration approved by Uhuu for your host. Do not assume an arbitrary MCP client or a generic client-secret flow is compatible.
Copilot availability must be confirmed with Uhuu before configuration. A Microsoft Entra application or Microsoft OAuth configuration alone does not establish a supported connection. Follow the Copilot prerequisites.
| Feature | Grant | Administrative implication |
|---|---|---|
| Template discovery, document drafts and revisions | documents:draft | Includes writes; this is not a read-only grant |
| PDF creation and artifact retrieval | documents:render | Opt-in in addition to draft access; separately confirm the saved revision and public-link disclosure |
| Studio proposals | studio:documents | Separate product and acceptance workflow |
| Studio file intake | studio:file-intake | Separate feature; approve only if needed |
| Approved Studio data references | studio:data-refs | Optional read feature |
| Configured Data Gateway reads | datahub:read | Read-only access to the team's approved sources; confirm the source access boundary |
These are feature grants, not individual-tool permissions. Review the actual consent screen and request only the features needed; the shared connection can request features beyond Documents. An existing draft-only grant remains narrow. Legacy uhuu:read and uhuu:write are not substitutes for these grants. Request only the documented capabilities enabled for your connection.
Enforced controls and conversational confirmation
The gateway and owning product enforce authorization, fixed-team boundaries, template/version pins, field policy, structural validation, revision checks, and idempotency. Documents operations recheck the person's platform access. Available tools can be narrowed by grants and enabled capabilities; tool discovery alone does not authorize execution.
The assistant must show the prepared content and obtain confirmation as described in the Documents workflow. The confirmation.confirmed flag is supplied by the host. It is not a server-issued receipt proving a human approved the exact payload. If your organization requires independently enforced human approval, confirm those requirements with Uhuu before adopting this workflow.
Data flow and exposure
| Data | Flow and review point |
|---|---|
| Conversation and brief | Processed by the selected AI host; sourced fields are sent to Uhuu in tool arguments |
| Template guides and saved document fields | Returned by authorized tools and available to the host/model; review what may leave Uhuu |
| Saved draft | Stored by Uhuu and opened through the returned editor handoff; editor sign-in may be required |
| Uploaded images | Originals and metadata are stored by Uhuu; CDN links are accessible to anyone holding them until deletion, with possible brief caching |
| Rendered PDF | PDF output is public by link; expiry of a handoff/download link does not revoke the underlying file |
| Optional DataHub reads | Results pass through the approved gateway and host; record source provenance and the credential's access boundary |
Use sample data for initial checks. Public-by-link images and PDFs need explicit approval for the intended data classification. A draft-only connection can omit these features.
Before production approval, obtain the applicable Uhuu and host-provider agreements and approved answers for hosting regions, subprocessors, retention/deletion, backups, model-data use, and telemetry/audit retention. This guide does not establish residency, certification, contractual retention periods, or a customer-accessible audit export. Request the applicable information through Uhuu support.
Network requirements
Separate cloud-to-cloud MCP traffic from the user's browser traffic. A successful connection from an administrator's laptop does not prove that the AI host can reach the MCP service.
| Connection | Requirement |
|---|---|
| Host service to gateway | HTTPS to mcp.uhuu.io on port 443; preserve authorization headers and MCP request/response handling |
| OAuth discovery and code/token exchange | Host access to auth.uhuu.io; supported exact callback and client authentication method |
| User sign-in and editing | Browser access to auth.uhuu.io, app.uhuu.io, and the editor/template asset domains |
| Optional in-host UI | Host sandbox/CSP compatibility, declared resource domains, and any approved cross-origin requests |
For editor assets and each published template's domains, use the Enterprise IT Checklist. It complements MCP connectivity; its iframe requirements apply to the Uhuu editor and do not imply a host supports embedded editing.
Disconnect, offboarding, and emergency access removal
Disconnecting removes the credential stored by the host; it does not guarantee immediate invalidation of every previously issued credential. Account for token lifetimes and Uhuu access checks when planning offboarding. Signing out of the Uhuu website alone does not revoke a connector connection.
For offboarding, remove the host connection and stored credentials, remove the user's agent/connector access, and remove the relevant Uhuu access as appropriate. Test subsequent tool calls and refresh behavior. Downstream access checks can refuse operations even while a signed access token has not expired, but do not promise immediate universal token invalidation.
If your organization requires immediate access removal, agree the supported removal procedure and timing with Uhuu before rollout. Ask Uhuu to confirm the applicable credential lifetimes and verify that the procedure meets your security requirements.