AI Conductor
Compose and edit Payload pages by chatting — grounded in your real block library, gated by your explicit approval.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirMost "AI page builder" demos fall apart in production for two reasons: the agent invents fields, blocks, or IDs that don't exist — and it writes to your database before anyone's looked at what it's doing.
AI Conductor fixes both. Every proposal is built from your real, live schema, so the agent can only use blocks and fields that actually exist. And it never touches your database until a human explicitly approves. The same grounded, approval-gated tool layer works two ways: as a chat panel inside your Payload admin, and as a standalone MCP server for external agents like Claude Desktop and Claude Code.
blocks field, no schema changes required.1. Install
pnpm add payload-ai-conductor
2. Register the plugin
import { buildConfig } from 'payload'
import { payloadAiConductor } from 'payload-ai-conductor'
export default buildConfig({
plugins: [
payloadAiConductor({
collections: ['pages'], // optional — omit to auto-discover every collection with a `blocks` field
}),
],
})
3. Regenerate your types (however you normally do it)
pnpm payload generate:types
4. Set a model key — either fill in the Settings screen now in your admin nav, or use env vars:
AI_CONDUCTOR_PROVIDER=anthropic
AI_CONDUCTOR_API_KEY=sk-ant-...
AI_CONDUCTOR_MODEL=claude-sonnet-5
Open AI Conductor in your admin nav — you're chatting.
Lock down the Settings screen. That screen holds your decrypted API key. Without a
settingsAccessrule, Payload's own default applies — any logged-in user, not just admins:payloadAiConductor({ settingsAccess: ({ req }) => req.user?.role === 'admin', // match your own role check })
Descriptions are optional, but they make proposals sharper. Pick whichever fits:
Inline, next to the block definition:
export const CallToAction: Block = {
slug: 'cta',
custom: {
aiConductor: {
description: 'A prominent call-to-action banner. Use mid-page, not at the top.',
examples: [{ heading: 'Ready to try it?', buttonLabel: 'Start free', buttonHref: '/signup' }],
},
},
fields: [
/* ... */
],
}
Markdown, with zero changes to existing block files:
payloadAiConductor({ blocksDir: path.resolve(dirname, 'block-docs') }) // looks up ./block-docs/<slug>.md
---
examples:
- heading: 'Ready to try it?'
buttonLabel: 'Start free'
---
A prominent call-to-action banner. Use mid-page, not at the top.
In the admin — click AI Conductor in the nav, or Ask AI Conductor on any document's edit view for page-scoped context. Attach an image to use it directly in a block, or a file just for context.
Over MCP — point any MCP client at your site, authenticated as a restricted (non-admin) Payload user:
{
"mcpServers": {
"ai-conductor": {
"url": "https://your-site.example.com/api/plugin/ai-conductor/mcp",
"headers": { "Authorization": "users API-Key YOUR_API_KEY" }
}
}
}
Exposed tools: list_collections, get_collection_schema, list_blocks, get_block_schema, search_documents,
propose_layout, revise_proposal, apply_proposal.
apply_proposal is the only tool that writes — only after validation, and, in chat, only after your approval.maxSteps / timeoutMs bound how long and how far a single turn can run.pnpm install
cp dev/.env.example dev/.env # set PAYLOAD_SECRET
pnpm dev # http://localhost:3400/admin
dev/ is a throwaway Payload install for developing the plugin itself — a small reference block library
(Hero, RichText, CTA, Grid, Testimonial) plus a public page-preview route.
pnpm lint
pnpm test:int # vitest — unit + integration
pnpm test:e2e # playwright — admin UI end to end
dev/eval.int.spec.ts runs the real agent loop against a live model with an LLM-judge rubric. It needs
AI_CONDUCTOR_PROVIDER/AI_CONDUCTOR_API_KEY/AI_CONDUCTOR_MODEL and skips itself otherwise, so the rest of the
suite stays green without a key.
MIT
Chat-driven page building for Payload CMS — grounded in your real blocks, gated by human approval. Embedded BYOK chat + MCP server included.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Payload Ai Conductor roda localmente via stdio.
Última verificação: 2026-10-28. Chat-driven page building for Payload CMS — grounded in your real blocks, gated by human approval. Embedded BYOK chat + MCP server included.