Documents MCP

Documents MCP lets an assistant prepare an editable document from an existing published Uhuu template. The template supplies the layout and field ownership contract, with an authored conversation guide when available. The assistant gathers the brief, fills permitted fields, and hands the saved draft back to you for review.

Availability

The integration is prepared for controlled use. Access depends on your team's approved connection, template access, and enabled capabilities. These instructions do not establish universal availability, marketplace approval, or a production rollout.

Before you start

• Use an MCP host with your team's approved Uhuu connection and an authenticated Uhuu account.
• Select a team with an accessible published template and document-draft permission (documents:draft).
• Provide a brief, files, or an explicitly authorized data source. DataHub is optional; a supplied brief can be sufficient.
• Keep the template's returned version and guide pins together: templateId, version, guideVersion, and guideDigest.

The unified Uhuu MCP entry point is https://mcp.uhuu.io; the Documents-focused entry point is https://mcp.uhuu.io/documents. Use the connection approved for your team rather than treating a URL as proof of access. Unified discovery prefixes these tools with documents__.

Prepare a draft

1. Choose a template. Search the published catalog, following pagination when necessary. Read its composition contract and any authored conversation guide before collecting answers. A draft-oriented contract describes fields the assistant may populate; protected layout, system, and editor fields retain their existing owners. A schema-derived contract is conservative field policy, not evidence of the author's intended narrative.
2. Gather the brief in the conversation. Follow the guide's intake order, ask for missing required facts, and distinguish supplied facts from assumptions. The document editor's chat is not a substitute for this intake.
3. Preview the proposed data. preview_document_draft checks the field structure and contract. A passing preview does not establish factual accuracy. Show material assumptions and request confirmation before creation.
4. Create and verify. create_document_draft saves an unrendered, editable draft after confirmation. Read it back with get_document to verify the actual populated fields, saved revision, and editor handoff. Retry an uncertain creation with the same idempotency key and unchanged request.
5. Review in Uhuu. Open the returned editor link, check content and assets, and make document-local edits. The published template remains the layout source.

If no suitable published template exists, ask the template owner to publish one. Documents MCP does not silently switch into layout authoring or create an arbitrary team or workspace. Template Studio covers the separate authoring and composition flow.

Images, revisions, and PDF export

Uploading images requires separate informed consent: Uhuu stores the originals and metadata, and anyone with an asset's CDN link can access it until deletion, with possible brief caching. Confirm transfer and placement, then verify the attached assets in the saved draft. Uploaded asset IDs are used for document updates; an arbitrary image URL is not an equivalent upload.

For revisions, read the current document first. update_document_draft requires an explicit requested change, confirmation, and the last-read baseRevision. A stale revision must be read and reconciled with editor changes before retrying.

PDF export additionally requires the opt-in documents:render permission. Review the current saved revision, confirm rendering, and disclose that the PDF is accessible to anyone with its link. render_document queues that revision; get_document_render reports progress. Treat the PDF as ready only when the result says it is ready and supplies the artifact. An expiring handoff link does not make the underlying public file private.

The result is an editable Uhuu document with a verified saved revision and, when separately requested and completed, a PDF. See the document lifecycle for how data, branding, templates, and rendering fit together.