Uhuu MCP integrations

Uhuu's remote Model Context Protocol (MCP) server gives an AI assistant tools to find published templates, prepare sourced content, and create or revise editable documents. The assistant conducts the conversation; Uhuu validates and saves the document. A person can then finish it in the Uhuu editor.

Access depends on the team's approved connection, permissions, template access, and enabled capabilities. Check host availability before choosing an integration, and confirm the supported connection with Uhuu.

Choose your guide

Task	Guide
Review authentication, access, data flows, and offboarding	Enterprise administration
Connect Claude, ChatGPT, or Microsoft Copilot and check availability	Host setup and compatibility
Understand installed skills, plugins, and optional UI extensions	Plugins and extensions
Prepare or revise a published-template document	Documents workflow
Test a connection and prepare an IT handover	Verification and troubleshooting

Architecture

AI host ── OAuth sign-in and consent ── auth.uhuu.io
   │
   └── authenticated MCP tools ── mcp.uhuu.io
                                    │
                                    ├── Documents: template contracts and saved drafts
                                    ├── Studio: composition proposals for human acceptance
                                    └── DataHub: explicitly configured reads

Person ── returned editor link ── Uhuu document editor

The host receives tool results and uses them in its model context. The gateway verifies the user, fixed team, audience, and granted features. Product services retain their access and validation checks. The public MCP bearer token is not forwarded as a backend API credential.

Connection settings

Setting	Value
Recommended shared endpoint	https://mcp.uhuu.io
Documents-focused endpoint	https://mcp.uhuu.io/documents
Transport	Streamable HTTP over HTTPS
Authorization server	https://auth.uhuu.io
OAuth resource/audience for both endpoints above	https://mcp.uhuu.io
Root protected-resource metadata	https://mcp.uhuu.io/.well-known/oauth-protected-resource
Documents protected-resource metadata	https://mcp.uhuu.io/.well-known/oauth-protected-resource/documents
Authorization-server metadata	https://auth.uhuu.io/.well-known/oauth-authorization-server

Use the exact supplied endpoint. Do not append /mcp to the shared root because a host's generic example uses that path. The historical /documents/mcp alias remains available; new Documents-only setups can use /documents.

The shared endpoint prefixes tools with documents__, studio__, or datahub__. Focused Documents tools are unprefixed: documents__get_document becomes get_document. Use the discovered names consistently.

Studio's focused /studio endpoint has the separate audience https://mcp.uhuu.io/studio; DataHub's /datahub audience is https://mcp.uhuu.io/datahub. They cannot be substituted for the Documents audience.

Prepare the team

1. Identify the approved Uhuu team and a user with the required role. Connector feature consent requires operator or owner access.
2. Have the template owner publish a suitable template with a usable field contract and, where authored, a conversation guide.
3. Approve the endpoint and requested features with the host administrator. For a Documents connection, start with documents:draft; PDF rendering additionally needs documents:render.
4. Complete the host's OAuth connection, confirm the intended team in consent, and read the connected team before preparing content.
5. Run the acceptance sequence with synthetic data.

One connection stays bound to its consented team. Switching teams in the Uhuu website does not retarget that grant. Previously narrower grants do not gain Studio, DataHub, or rendering access through refresh; additional features require fresh consent.

Shared product boundaries

Documents MCP fills an existing published template. Template Studio composes a proposal against published Roles and Looks and requires human acceptance before editable-document handoff. Neither route silently authors an arbitrary missing layout.

DataHub is optional. Gateway reads are limited to the team's approved sources and the access configured for that gateway; a user's Uhuu sign-in does not grant additional source-system permissions. Dataset authoring and writeback are outside this connection. A connection without configured gateways can legitimately return no gateways.

The same backend workflow can serve several hosts. Host-specific authentication, package distribution, file APIs, UI support, and tenant approval still require separate verification.