Unlayer Cloud API and hosted MCP

Unlayer is automatable today through the Cloud API at https://api.unlayer.com and a hosted MCP server. Cloud API v3 accepts a project API key, prefix unlayer_sk_, or a personal access token, prefix unlayer_pat_, as Authorization Bearer. API keys are bound to one project. Personal access tokens must pass projectId or X-Project-Id for project calls. OAuth access tokens are limited to the MCP server and are not accepted on Cloud API routes. The Cloud API manages templates, renders HTML, PDF, image, and ZIP artifacts, validates and converts design JSON, and can send transactional email from a verified domain. Email sending is in private beta. The TypeScript SDK is @unlayer/sdk. The authentication page also names a CLI that uses the same bearer tokens; this pass did not open its command reference, so the CLI is not scored. The MCP server is https://api.unlayer.com/mcp, with 14 tools and OAuth 2.1 PKCE or a bearer API key or personal access token. Generation and import tools open a temporary editor session and do not change saved project templates until a person saves. Connector catalogs were not opened. Computer-use viability is unassessed. API scores 7 and is the best path. MCP scores 6 because the main generation flow does not persist templates by itself.

Best path today: api · Overall automatability: 7/10