Skip to content

Codex and Creatify MCP

Creatify's official remote MCP endpoint is:

text
https://api.creatify.ai/mcp

What it adds

  • Video-ad orchestration from a brief or product URL
  • Product extraction and brand context
  • Shared brand decisions across supported runtimes
  • Workspace skill publication
  • Asynchronous task polling and finished-video downloads

Codex plugin in this repository

The repository includes plugins/creatify-codex-production-suite with:

  • Official remote MCP declaration
  • A production-routing skill
  • Browser-control reference
  • SEO and GEO video brief
  • Cost, publishing, healthcare, and QA gates

Existing Merlino skill inventory

The canonical ecosystem currently contains seven Creatify skill folders:

SkillCurrent role
creatifyBroad Creatify reference and routing
creatify-apiDeterministic API operations
creatify-agent-browser-productionAuthenticated Agent and browser work
creatify-custom-avatarCustom-avatar production
creatify-custom-templatesPlaceholder only, not an operational production skill
creatify-productionProduction standards and delivery
creatify-video-pipelineVideo pipeline orchestration

Only four of those folders were present on the active Codex runtime shelf during the 2026-07-31 audit. The plugin skill in this repository supplies the verified browser, MCP, SEO and GEO, editor, cost-gate, and QA guidance without pretending the placeholder is production-ready.

Authentication

Install the plugin, connect the Creatify MCP, and authenticate interactively with the Creatify account. Do not store credentials in the repository or plugin manifest.

Creatify browser authentication and Creatify MCP authentication are separate sessions:

  • A logged-in Creatify tab proves the browser session is authenticated.
  • codex mcp list must independently show the Creatify connector as logged in before MCP tools are considered operational.
  • Do not report the browser as logged out merely because MCP OAuth is incomplete.

Codex browser plugin

The authenticated in-app browser lane requires the bundled Codex browser plugin to be enabled:

powershell
codex plugin add browser@openai-bundled --json

Verify the plugin reports installed, enabled in codex plugin list. A task that started before the plugin was enabled may still have an empty browser-tool inventory. Start a new Codex task or reload local Codex plugins so the task receives the browser controls. This reload does not log out of Creatify or reset any Creatify project.

Verification

The connection is operational only after Creatify tools appear and a read-only call succeeds. If the MCP is unavailable, use the authenticated browser for visual work and the documented API for approved deterministic jobs.

App boundary

A Codex .app.json entry requires a real allocated connector or app identifier. This repository does not invent one. The plugin supplies the official MCP declaration now, and an app manifest can be added after Creatify or Codex issues the connector identifier.