MCP host setup and compatibility

Use the shared settings, then configure your approved host below. Availability depends on your Uhuu team, host account, organization policies, and enabled capabilities.

Host availability

Host	Connection route	What to confirm
Claude	Approved custom remote MCP connector	Organization permission, individual Uhuu sign-in, team access, and enabled document tools
ChatGPT	Approved custom MCP connection	Workspace policy, individual Uhuu sign-in, team access, and enabled document tools
Microsoft Copilot	Confirm availability with Uhuu before configuration	These guides do not establish a generally available Uhuu Copilot integration; see Copilot prerequisites
Other MCP clients	Confirm compatibility with Uhuu	Supported OAuth client, transport, callbacks, and required capabilities

Use the full Uhuu editor through the returned document link to finish editing. In-chat UI, attachment handling, PDF export, and installed workflow skills depend on the approved connection and host. Only rely on capabilities explicitly enabled for your organization. Contact Uhuu support to confirm availability.

Claude remote connector

An authorized organization administrator adds the remote connector under Organization settings → Connectors; members then connect individually. Individual-account setup is under Customize → Connectors. Claude's remote connections originate from Anthropic infrastructure, including when using Claude Desktop. Refer to Anthropic's current setup and network guidance for account-specific controls.

1. Add a custom web/remote connector with the approved Uhuu endpoint. Prefer https://mcp.uhuu.io for the shared connection; use /documents when a Documents-only connection is approved.
2. Use OAuth sign-in with Claude's supported published identity or supported automatic registration. Do not replace it with a copied Uhuu API token or a shared account credential.
3. Sign in to Uhuu, select the intended team in consent, and review the requested features.
4. Enable the connector for the conversation and ask it to identify the connected team and available templates. Run the acceptance sequence.

Use Open draft in Uhuu to access the complete editor and dialogs. Return to the conversation and read the latest revision before continuing. Embedded UI and file handling vary between hosts; keep enterprise browser protections enabled.

ChatGPT custom MCP connection

OpenAI's current setup uses ChatGPT Plugins → Add custom MCP server, with account and workspace policies controlling availability. Test the server and then the complete installed package separately. Follow OpenAI's connection and evaluation guide for the current host flow.

1. Create a custom MCP connection using the approved Uhuu URL exactly. Uhuu's root URL is already an MCP endpoint; do not append the generic example's /mcp path.
2. Configure OAuth, finish Uhuu sign-in, and review the selected team and features. Install/enable the resulting personal connection as required by the host.
3. Start a new conversation, select the connection, and perform the shared acceptance sequence with a published template.
4. After gateway tool/resource changes, refresh the connection's tools and open a new panel before retesting. Keep CSP enabled during UI verification.

Bundled onboarding and preparation skills require their own approved installation/distribution path; they are not installed merely by entering the endpoint. See plugins and extensions.

Microsoft Copilot

This guide covers Microsoft's options for connecting external MCP services to its business Copilot experiences. GitHub Copilot is a separate host and is not covered here.

Confirm availability with Uhuu

These instructions do not establish a generally available Uhuu Copilot integration or a ready-to-install Uhuu Microsoft agent. Contact Uhuu support before configuration. The setup steps below apply only after Uhuu has confirmed a supported connection for your organization and supplied the required OAuth settings.

Choose the route

Requested outcome	Route	Connection and workflow
Give an existing Copilot Studio agent Uhuu tools	A: Add the remote MCP server as a tool	Shared server, template contracts, document operations, workflow instructions
Make a named Uhuu agent available inside Microsoft 365 Copilot	B: Package a declarative agent with an MCP plugin	Same backend and workflow, with Microsoft-specific agent instructions, manifests and tenant distribution

Both routes need the shared connection settings, enterprise review, and a suitable published Uhuu template. They do not require a second document backend.

Confirm availability before configuration

Prerequisite	Contact	Required information
Availability for your chosen Microsoft route	Uhuu support	Approved endpoint, supported capabilities, and installation route
OAuth configuration	Uhuu and your Microsoft administrator	Supported registration mode, callback, token authentication method, resource, and scopes
Uhuu account and content	Your Uhuu team administrator	Eligible user, team access, and a suitable published template
Tenant access and distribution	Your Microsoft administrator	Approved environment, users, policies, and distribution process

For a Microsoft 365 OAuth plugin, Microsoft's documented runtime callback is https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect. Its tooling guidance also identifies https://vscode.dev/redirect for tool discovery. Confirm the required callbacks with Uhuu. For Copilot Studio, use the callback produced by the approved connector configuration; do not assume it is the same as the declarative-agent callback. Microsoft OAuth configuration, MCP Apps server requirements

Use only the OAuth configuration supplied for the approved connection. Registering a Microsoft Entra app or selecting dynamic discovery does not by itself establish compatibility. Do not substitute shared API tokens, another provider's callback, or disabled authentication.

Administrator preparation

Record the tenant, environment, region, target Microsoft experience, required licenses/billing, administrator and maker access, approved users, and nonproduction test data. Confirm that custom app upload or the selected distribution mechanism is permitted. Use Microsoft's current development prerequisites rather than assuming a product license alone provides every prerequisite.

For Copilot Studio, the environment administrator must approve the Uhuu connector's data-policy classification and its combination with other connected sources. Microsoft data-policy guidance

Uhuu prerequisites are an approved team connection, an operator/owner able to consent, access to a published template, and documents:draft. Check the text-to-draft workflow and Uhuu editor handoff using sample content before adding optional images, UI or rendering.

Route A: Copilot Studio agent with MCP tools

For a Uhuu-approved connection:

1. Open the chosen agent's Tools page, add a tool, and choose a new Model Context Protocol server.
2. Enter a clear name/description and the approved server URL. Use https://mcp.uhuu.io for the shared connection, or https://mcp.uhuu.io/documents for an approved Documents-only connection.
3. Choose OAuth and use the registration mode and settings supplied by Uhuu. Select dynamic discovery only when it is supported for your approved connection.
4. Create a connection, sign in to Uhuu as the intended user, review the team and scopes, and add the server to the agent.
5. Inspect discovery, apply the shared workflow instructions, and test with the intended end-user identity.

Microsoft also documents a Power Apps custom-connector route using an OpenAPI definition with x-ms-agentic-protocol: mcp-streamable-1.0. Use it only with a reviewed connector definition and working OAuth configuration. Microsoft's wizard and custom-connector instructions

Use discovery for tool names. The shared server exposes documents__search_templates, for example; the focused server exposes search_templates. Verify the connected team and the saved draft before enabling the agent for additional users.

Route B: Microsoft 365 declarative agent with an MCP plugin

For a Uhuu-approved connection:

1. Install Visual Studio Code and the Microsoft 365 Agents Toolkit version required by Microsoft's current walkthrough.
2. Create a Declarative Agent, add an action, and choose the MCP-server starting point.
3. Supply the approved Uhuu URL and the authentication mode validated with Uhuu. Let the toolkit generate the agent and plugin configuration.
4. Add the shared document workflow to the agent's instructions. Inspect the discovered tool set; review any generated dynamic discovery or curated tool configuration.
5. Sign in to the test tenant, provision and sideload the generated project using the toolkit, then open the agent in Microsoft 365 Copilot.
6. Complete Uhuu sign-in as a test user and run the shared acceptance sequence.

These steps adapt Microsoft's MCP-backed declarative-agent walkthrough. A package made for ChatGPT or Codex is not a Microsoft app package.

For an OAuth MCP plugin, Microsoft uses an OAuth auth-configuration reference such as OAuthPluginVault; secrets belong in the supported credential store, not the app manifest. The Uhuu-approved flow determines whether static or dynamic client registration is usable. Microsoft OAuth configuration

Provisioning and sideloading establish a development installation. The customer administrator must separately approve and distribute the exact tested Microsoft package through the tenant's supported process. Record package ownership, intended users and update/removal procedures before wider availability.

Optional in-chat UI

Microsoft documents MCP Apps support, but its current compatibility table excludes openai/fileParams, file upload/download helper APIs, and CSP frameDomains. It supports only part of the broader UI/extension surface. Microsoft capability table

Confirm any in-chat UI capabilities with Uhuu before enabling them. Use Open draft in Uhuu for the full editing experience. Microsoft host support for a UI API does not establish that the capability is included in your Uhuu connection.

Organization acceptance and handover

Run verification and troubleshooting for the approved route. Check authentication, refresh, team access, sourced intake, draft readback, conflict recovery, and access removal. Review approval and offboarding requirements with Uhuu before organization-wide use.

The handover should identify the approved route, installation method, users and scopes, data classifications, acceptance date, limitations, support contact, and removal procedure. Keep the connection restricted to the agreed users until your administrator has approved wider use.

Other MCP clients

For any other client, confirm Streamable HTTP, authorization-code flow with S256 PKCE, discovery, exact audience handling, callback support, and refresh behavior with Uhuu before configuration. A generic MCP client configuration does not establish compatibility. Local-code execution and attachment APIs must also be checked independently.