Troubleshooting Templafy MCP Server

Updated May 29, 2026 14:12

This article describes how to troubleshoot common issues with Templafy MCP Server.

MCP Server module enabled.
Library and Universal Document Agent or Custom Document Agent modules enabled.
Each end user needs an active Templafy account in the same organization.
An AI assistant that supports adding remote MCP servers as connectors, with a plan that allows custom or third-party connectors.
Outbound HTTPS to the Templafy MCP endpoint and to the Templafy platform, https://*.templafy.com/**, must be allowed for users and the assistant's OAuth flow.

Sign-in window closes immediately, or shows an error

Confirm you signed in to the correct Templafy organization. Multi-organization users should make sure they pick the right one when prompted.
Browser pop-up blockers can stop the OAuth window from opening — allow pop-ups for the AI assistant's domain and for templafy.com.

The assistant requires pre-registration but is being used as if it supports CIMD. The customer AI assistant admin or partner should contact their Templafy team to arrange registration, then enter the resulting Client ID in the assistant.
If the assistant was pre-registered, double-check with your Templafy team that the redirect URI registered on the Templafy side exactly matches the one the assistant is sending (including http vs. https, trailing slashes, and path).

Your organization may not yet have published any agents or themes that match your role. Ask your Templafy administrator to confirm what's published in the admin portal.
Ask the assistant: "Use the Templafy connector to list my themes." If the list is empty, the issue is on the organization side.

This is most often caused by an unusually long generation. Wait 5-7 minutes and ask the assistant to retry — the connector will resume the existing session.
If it happens repeatedly for the same prompt, shorten the prompt (fewer slides, shorter description), or try the same prompt in the assistant's web UI. If the issue persists, contact Templafy support with the time of the failure.

The connector returns a short, sanitized error message describing the problem. Common causes are an out-of-date agent or theme ID (the assistant picked one that was unpublished in the meantime) or a transient downstream issue.
Ask the assistant to list agents again or list themes again and retry. If the error persists, contact support.

tech_role Document Agents