MCP plugins and extensions
Uhuu integrations use a remote MCP backend and a template-driven document workflow. A host integration can use that foundation with its own packaging, authentication, and optional user interface. See host availability before choosing an installation route.
What each layer provides
| Layer | Purpose | Reuse boundary |
|---|---|---|
| MCP connection | Authenticated discovery and product operations | Reuse Uhuu's endpoint, contracts and validation; each host needs a supported OAuth client |
| Workflow instructions / skills | Template selection, sourcing, intake, preview, confirmation and recovery | Adapt the canonical workflow to the host's instruction mechanism and discovered tool names |
| Optional MCP Apps UI | Template browsing, intake, document status, and editor handoff | Use only capabilities enabled for your connection and supported by the host |
| Optional host extensions | Composer mentions, workspace entrypoints, context and file integration | Availability depends on the approved integration; these are not all portable MCP features |
| Installable plugin or agent | Distribution, identity, assets, instructions, and service connection | Build and verify a package for the target host |
OpenAI plugins can combine skills, MCP configuration, and optional UI. The shared MCP Apps standard is the starting point for UI portability. OpenAI plugin architecture
Connection and installation
An MCP connection gives the host access to the tools authorized for your Uhuu team. Installing a plugin or agent can also supply workflow instructions and host-specific entrypoints. Entering a server URL alone does not install those additional instructions.
Use the installation method supplied by Uhuu and approved by your organization. Confirm the available capabilities and distribution route with Uhuu support. These guides do not establish a public marketplace listing or availability of a particular package.
The shared Documents workflow describes template selection, sourced intake, preview, confirmation, saving, and readback. Host instructions should follow that sequence and use the tool names discovered through the approved connection.
Reuse in a Microsoft agent
After confirming availability with Uhuu, use the Microsoft Copilot section to configure a Microsoft-specific agent/package around the MCP service. Packages for other hosts are not interchangeable with Microsoft app packages. Adapt the workflow instructions, use approved branding assets, and validate the generated Microsoft manifests and OAuth configuration.
The following example instructions capture the shared behavior. They do not replace the selected template's full returned guide or install a workflow skill:
Use only the approved Uhuu connection and its discovered tool names.
For an existing published-template document, read its composition contract
and conversation guide before preparing content. Retain the returned pins.
Conduct intake in this conversation. Reuse supplied facts and ask for missing
required facts; distinguish sources and assumptions. Do not relay intake to
the document editor's embedded assistant.
Preview the permitted fields, show the proposed content, and obtain the
required confirmation before saving. Verify saved fields and revision by
reading the resulting document. Keep the same creation key on an unchanged
retry. Before revisions, read the latest document and reconcile conflicts.
Return the Uhuu editor handoff. Request image transfer or PDF rendering only
when separately authorized, with the relevant public-link disclosure and scope.
If no suitable published template exists, explain the gap. Use Studio only
for its requested proposal workflow; it requires human acceptance in Uhuu.These instructions guide the model. They do not implement a server-enforced human approval receipt; review the confirmation boundary.
ChatGPT-specific extensions
OpenAI documents optional extensions into sidebar, composer, and file experiences. Support varies by host and surface; a platform capability is available to your Uhuu connection only when explicitly enabled. OpenAI extension documentation
Treat extension availability separately from ordinary tool calls. Do not assume composer mentions, attachment APIs, native forms, or embedded editing are included just because the host supports MCP. Follow the supported controls shown in your approved connection.
The common editing path is to prepare the document in conversation, open the full Uhuu editor, then reread the saved revision on return. This keeps the document workflow usable without depending on optional host extensions.
Organization acceptance
Record your approved installation method, enabled capabilities, granted scopes, and responsible administrator. Check the actual installed workflow in a fresh conversation. A working MCP connection does not establish that additional workflow instructions were installed.
After an integration update, repeat the affected acceptance checks before making it available to more users.