Content Engine
Tell ChatGPT or Claude what website you want to connect. The assistant handles the development work. You complete the account sign-ups, any required sign-in screens, and decisions through chat. You do not need to hire a separate developer or edit the integration by hand.
Neon is required for the database. The plugin includes the Payload CMS MCP integration and a setup skill that installs it in your project. WorkOS protects the connection to your CMS. Each customer uses their own website and accounts.
Start in the desktop app
- Open the plugin controls in Claude desktop/Cowork or ChatGPT desktop/Codex.
- Add the Content Engine repository as a marketplace where your host supports that flow, or upload the supplied plugin ZIP through its supported upload control.
- Install Content Engine from Notorious Llama Content Engine. Give the assistant access to the folder containing your website.
- Choose the plugin's setup action where available. In Claude, you can use
/content-engine:setup-content-engine. You can also send this request:
Set up Content Engine for my website. Use Neon and handle the development work. Ask me for account sign-ups and decisions through chat. Install the included MCP integration, check it, and connect it to this assistant when the host supports that step.
The assistant starts with the bundled setup skill, identifies React, Next.js, Svelte or SvelteKit, and follows the matching integration. It prepares the code and configuration, uses the included integration installer, and checks its work. It asks you to create the required Neon, WorkOS and hosting accounts and to complete necessary sign-in or approval screens.
Automatic setup depends on the tools available in that assistant session. If the host cannot perform a deployment or connection step, the assistant identifies that specific missing capability. Installing the plugin alone does not create external accounts, authorize OAuth, or prove that a live CMS is connected.
Seven included skills
| Skill | What the assistant does |
|---|---|
setup-content-engine | Runs chat-led setup with Neon and installs the included CMS integration. |
react-to-payload | Connects a React website to Payload CMS while preserving the website. |
nextjs-to-payload | Adds or integrates Payload in a Next.js website. |
svelte-to-payload | Connects Svelte or SvelteKit to Payload CMS. |
seo-aeo-stinger | Checks and implements SEO/AEO for the website's actual framework. |
blog-content-stinger | Researches, drafts, reviews and saves blog content. |
google-search-console | Optionally guides site verification and sitemap registration, with computer-control or manual steps. |
Seven flat files under commands/ load those same skills for Claude/Cowork. They are host invocation adapters, not extra workflows, skills, Drones or Pest Controller dependencies. OpenAI hosts use the portable skills; the manifest's setup action remains setup-content-engine. Google Search Console is optional and does not run automatically.
After setup
For the first article, ask:
Use Content Engine's Blog Content Stinger to prepare one sourced article for my audience. Discover our authors and tags, show me the brief and draft, and save an unpublished draft after I authorize the CMS write.
For search setup, ask:
Use Content Engine's seo-aeo-stinger on this website. Identify its framework first. Check the public page, metadata, sitemap, draft privacy and structured data, then show me the results.
Where the host supports namespaced invocation, use /content-engine:blog-content-stinger or /content-engine:seo-aeo-stinger. Select this plugin's skill when another installed plugin has the same name. The local SEO adaptation does not replace the upstream installation.
For optional Google Search Console help, ask:
Use Content Engine's google-search-console skill to help verify my website and register its sitemap. Use computer control if available, or guide me manually. Leave the final Save for any DNS or domain change to me.
You can use /content-engine:google-search-console where supported. For DNS and domain changes, the user clicks the final Save. The assistant must not bypass that step with an API, keyboard shortcut or another submission route. Search Console is not required for the CMS to work.
The shared domain-change control applies across all seven skills, including verification changes and forms that may autosave.
The content MCP creates drafts and imports images. You review and approve a named draft in chat. The assistant needs a separately authorized CMS editor or browser route to publish it. A draft article's privacy does not make its imported images confidential; the supplied media collection is public.
How the included MCP connects
The MCP package contains its source, integration installer, tests and setup details. The setup assistant installs that source into the customer's project and prepares the customer's own endpoint. Generic mcp.json and .mcp.json connection maps begin empty so installation cannot connect to another customer's CMS.
After a deployment exists, setup wires its real HTTPS endpoint through the host's supported connection flow. Claude's connection uses type: http; the portable OpenAI connection uses type: streamable-http and declares OAuth. WorkOS sign-in and permissions must still complete successfully. The assistant reports the actual observed result and keeps secrets out of chat, committed files and release manifests.
Host policies may restrict custom MCP connections or plugin installation. A remote MCP connection alone does not install local skill files. The included setup skill distinguishes installing the plugin, installing the integration, deploying the service and authorizing the connection.
Official host details: OpenAI packaging and connection testing.