MCP verification and troubleshooting

Use this sequence when setting up or updating your organization's approved Uhuu connection. Use sample data and a suitable published template. Only create, update, upload, or render content within the scope authorized by your administrator.

Before you begin

Confirm the host's availability, approved endpoint, intended Uhuu team, and required permissions. Your host administrator should approve the connection and the data that may be processed through it.

Check the complete document workflow using the actual approved account. Successfully reaching an endpoint or listing tools is not enough to confirm that content can be prepared, saved, and reviewed. Record any omitted capabilities in your organization's handover.

Acceptance sequence

1. Authenticate. Use a fresh connection as the intended user. Check discovery, sign-in, consented team, requested features, and connection refresh. For Copilot, first confirm availability and settings with Uhuu.
2. Confirm access. Read the connected team and catalog with the discovered tool names. Follow pagination. Use an approved negative case to show that another team's resource is refused; do not probe unapproved customer data.
3. Read the template. Retain templateId, version, guideVersion, and guideDigest from the actual contract. Check its field ownership and authored conversation guide. No suitable published template is an honest blocking result.
4. Prepare sourced content. Supply a synthetic brief with known expected values. Check that the host reuses supplied facts, asks only missing required questions, and does not send intake to the editor's assistant. Verify cancellation produces no draft.
5. Preview and create. Review the prepared fields and assumptions. After confirmation, create one draft and read it back. Compare saved field values with the expected content, document identity and saved revision. Structural preview alone is insufficient.
6. Recover an uncertain create. In an approved recovery test, repeat the unchanged creation request using the same idempotency key. Verify it returns the same draft. Do not run this test by changing keys and creating duplicates.
7. Edit and resume. Open the draft in Uhuu, change one synthetic field, and save. Return to the conversation and read the new revision. Request a separate change and verify both values remain correct.
8. Exercise a conflict. Attempt an approved update with a stale baseRevision. Expect refusal; reread, reconcile the external change, review again as needed, and retry from the current revision. Verify untouched fields remain intact.
9. Test removal. Remove the host connection/stored credentials and the relevant Uhuu access as planned. Check calls and refresh behavior, retaining observed timing. Follow the agreed access-removal procedure.

Check optional capabilities separately

Capability	Required additional check
Installed workflow skills	Install the exact package, start a fresh conversation, and verify its instructions activate; entering an MCP URL is not skill installation
In-host UI, if enabled	Keep the host's normal CSP. Check template assets, reviewed save, conflicts, editor handoff, and conversation resumption
Uploads	Confirm transfer/public-link disclosure; use the supported host representation; verify accepted asset IDs and placements in the saved draft
PDF rendering, if enabled	Obtain documents:render through consent, approve the current saved revision and public-link disclosure, wait for readiness, and download/visually inspect the generated PDF
User access	Sign in as the intended user and confirm their team, role, template access, and available tools
DataHub	Verify the team's approved read-only sources, access boundary, declared tool schemas, and source provenance

For PDFs, check revision matching and the agreed retry/deletion behavior. A draft or queue acknowledgement is not a finished document. Confirm that rendering is enabled for your organization before including it in the workflow.

Troubleshooting

Symptom	Check and recovery
invalid_redirect_uri / unsupported client	Check the exact callback and client settings supplied for the approved connection. Confirm availability with Uhuu; do not substitute a different provider's callback.
Client-secret or token exchange failure	Check the approved token authentication method, PKCE, exact callback and resource. Do not assume a generic manual OAuth form is compatible.
401 after connecting	Inspect the OAuth challenge, expiry, issuer, audience and refresh. Reauthorize through the supported host flow when required.
403, missing feature or scope step-up	Check team access, role, granted features and enabled capability. Tool visibility does not authorize execution. Obtain fresh consent for additional features.
Empty template catalog	Verify the fixed consented team, template publication/access and pagination; do not create an arbitrary workspace to conceal missing access.
Missing tools or stale panel	Check granted permissions and enabled capabilities; refresh the connection after an update and open a fresh panel. Confirm shared versus focused tool names.
Blank embedded editor or missing assets	Check host CSP/frame support and deployed assets. Use the returned Uhuu editor link, then reread the revision. See the IT checklist.
Image transfer fails	Use the file handling supported by your approved connection. Keep accepted assets and recover the failed items; verify attachment by reading the saved draft.
Stale revision	Read the latest document, reconcile changes and retry using its revision; do not overwrite an external edit silently.
PDF still queued, failed, or unavailable	Poll the existing job and inspect its state; avoid resending an uncertain enqueue. A draft, thumbnail, or expiring handoff link is not a private finished PDF.

Handover record

Provide the following record to the customer administrator. Keep tokens, signed upload URLs, cookies, credential-bearing traces, private conversation URLs and confidential document values out of shared reports.

Acceptance date and responsible administrator:
AI host and connection name:
Tenant and environment (approved identifiers only):
Uhuu team and test template/version/guide pins:
Endpoint and OAuth resource:
OAuth client profile, callback and granted scopes:
Approved installation method and agent/connector name:
Checks passed, failed and omitted; sanitized evidence references:
Verified optional capabilities:
Approved users and data classifications:
Known limits and follow-up actions; responsible contacts:
Support contact and incident route:
Access-removal observations, rollback and package-removal procedure:
Tenant approval owner/date and rollout scope:

Refresh this record after relevant integration changes and obtain your administrator's approval before expanding access.