AI and agents

AI that writes like your brand. Agents that never publish.

Leiho uses the AI provider configured in WordPress, with your brand context. And your own agent, Claude, Codex, Cursor or Gemini, can draft content and check your setup over MCP.

01

Brand context

Tone of voice, audience, words to prefer and avoid, forbidden claims and mandatory facts, sent with every request.

02

AI on every text field

Generate, rewrite, shorten, expand, fix, change the tone or translate. The proposal opens as a diff.

03

Nothing saved behind your back

Accepting a proposal writes into the field like typing. Undo works, nothing is saved until you save.

04

Your provider, your key

Leiho stores no API key and picks no provider: it uses WordPress’s own AI connectors (WordPress 7.0+).

05

Agents over MCP

With the official MCP Adapter, agents read your content model, search entries and create drafts.

06

Setup by agent

Administrators can let an agent run diagnostics and fix settings, then revoke its password.

Connect your agent

Leiho → AI gives a ready configuration for Claude Desktop, Claude Code, Codex, Cursor, VS Code with Copilot, Gemini CLI, Windsurf and any client that runs local MCP servers.

Terminal
codex mcp add mysite \
  --env WP_API_URL=https://cms.example.com/wp-json/mcp/mcp-adapter-default-server \
  --env WP_API_USERNAME=editor \
  --env WP_API_PASSWORD='xxxx xxxx xxxx xxxx xxxx xxxx' \
  -- npx -y @automattic/mcp-wordpress-remote@latest

Drafts only

Content abilities read, and write drafts only. An agent works with the rights of the user it connects as: give it an editor account and an application password you can revoke.

Edit the real site.

Free and open source. Try it on a real WordPress, in your browser.