For devs already running their own AI stack
Already piloting WordPress with Claude? Skip our admin chat.
If you have Claude Code (or Cursor, ClawBot, Hermes, your own MCP harness) already wired into your WordPress, our admin chat is mostly redundant for you. We’ll say it before our sales page does. But there are four things you’d still have to build yourself — and we ship them.
No fluff · No upsell to features you already own · Honest tier recommendation at the bottom
The honest part
If you already pilot your WP with an MCP-enabled agent, our admin chat doesn’t move the needle.
Your Claude Code session already has shell, your MCP server already has wp_create_post and friends, your audit trail is your terminal scrollback. We aren’t going to convince you that one more chat surface in wp-admin is worth €29/month — because for you, it isn’t.
What we’d like you to understand is that the WordPress plugin we ship is not really “an admin chat.” It’s an opinionated bundle: a WP-native MCP server with 16 audited tools, a public-facing chat widget, a JSON-LD/llms.txt/agent.json discoverability layer, and a JWT-based capability scoper. The admin chat happens to be the most marketable piece — but if you already have your own AI harness, it’s not the piece you should care about.
So: read the next four sections, decide if any of them solve a problem you have, and pick the cheapest plan that covers them. We won’t cross-sell.
The four pieces
What you’d still have to build.
01 · The actually-hard one
A visitor chatbot you can’t replicate with your personal Claude.
Anonymous web traffic can’t auth to your personal Claude session. There’s no public OAuth flow that makes sense for “random visitor on landing page wants to ask about pricing.” You’d need a hosted backend with rate-limiting, conversation memory, content moderation, OTP/JWT visitor auth, capability sandboxing, and a streaming SSE wire — all wrapped around an LLM call you’re comfortable exposing to the internet.
What we ship: a ~30KB widget served from your domain that talks to api.animam.ai, with all of the above. The visitor agent is scoped, content-policy filtered, rate-limited, IP-tracked, GDPR-clean. You couldn’t build this in a weekend, and even if you could, you don’t want to be the one paginated against a token bill at 3am.
02 · Pre-built tool catalog
A WP MCP server with 16 audited tools — point your own Claude at it.
If you wrote your own WP MCP server, you wrote wp_create_post and wp_publish_post and felt clever. Then you noticed your agent kept asking for an SEO audit, so you wrote wp_seo_audit. Then bulk image-alt fixing, scheduled posts, term assignment, draft search, RankMath/Yoast meta detection, REST escape hatch… two weekends in, you’re maintaining a tool catalog.
What we ship: 16 tools, including wp_seo_audit, wp_set_image_alt_bulk, wp_set_seo_meta (auto-detects RankMath/Yoast), wp_schedule_post, wp_rest_call (escape hatch), wp_get_post_meta + wp_set_post_meta (low-level for builder-aware adaptation). Plus bridges: WooCommerce (4), MailPoet (2), WPForms (dynamic per form). The plugin is the MCP server. Connect your Claude to it with your tenant secret. Skip three weeks of yak-shaving.
03 · Multi-user scoping
Capability scoping the moment it’s not just you on the keyboard.
Your personal Claude with admin creds works because there’s exactly one principal: you. The model is single-user superuser, the audit log is “trust the human.” That model breaks the moment you have an editor, a junior, an agency client, or any agent triggered by something that isn’t you typing.
What we ship: JWT short-lived (15min) with the WordPress user identity, capability check on the WP side before each tool call, immutable audit log entry per call (CPT, exportable). An editor user gets a tool catalog that’s a strict subset of an admin’s. A team of five with one Animam plugin gets five distinct, audit-trailed agent surfaces — without you wiring OAuth.
04 · Discoverability layer
The agent-readable web stack, generated from your WP content.
External agents — Perplexity, Claude.ai web, ChatGPT search, internal scrapers — increasingly read sites through a discoverability stack: llms.txt, llms-full.txt, /.well-known/agent.json, /.well-known/llmfeed, /.well-known/mcp.json, JSON-LD Organization, agent-friendly robots.txt. You can build all of this; it’s ~2 days of yak-work and a recurring sync problem.
What we ship: all six files, generated from your published content, refreshed on save_post, with a built-in “Discoverability Coach” that flags missing meta. JSON-LD on every page. X-AI-Generated response header on assistant outputs (RGPD/AI Act ready). When the day comes that “agent traffic” counts as much as “Google traffic,” your site already reads.
Pick the cheapest tier that fits
Honest tier recommendation.
If all you want is the visitor widget + discoverability:
→ Visitor plan, €19/month. Widget, knowledge sync, discoverability files. You keep piloting WP from your terminal. We keep our admin chat to ourselves.
If you want the visitor widget AND want to point your own Claude at our pre-built MCP toolbelt:
→ Bundle, €39/month. Same widget, plus the plugin’s MCP server is unlocked for external connections. Your Claude Code / Cursor / Hermes hits your-site.com/wp-json/animam/v1/mcp with your tenant bearer, gets 16 tools. (We can also turn off the in-admin chat surface from settings — your wp-admin stays clean.)
If you don’t need a visitor widget:
→ Don’t pay us. Open-source WP MCP servers exist. Roll your own, or fork one. We’re for the people who also need the public-facing chat or the agent-discoverable site. If those don’t solve a problem you have, save your money. We’ll be here when the public agent traffic shows up in your analytics.
Questions a brochure can’t answer? [email protected] — answered by someone who’s also got Claude Code in another tab.
On the roadmap
Coming: Animam Vanilla.
The unbundled version. Built explicitly for you.
Everything we just described — minus the WordPress plugin, minus the widget chrome, minus the dashboard, minus the opinions about wp-admin. Just the primitives: the MCP server, the tool registry, the JWT capability scoper, the discoverability generators, the conversation backend, the visitor-auth flows.
Drop them into your own stack. Compose them. Skin them. Mount them on something that isn’t WordPress. The current plugin will keep being the “batteries-included” product for non-devs; Vanilla is for the people who’d rather bring their own batteries.
Ship date: not committing yet. Pricing: not committing yet. What we will commit to: emailing you when we are.
Built by people who also have Claude Code in another tab.
Developers — frequently asked questions
What stack does the Animam WordPress plugin run on?
PHP 7.4+, WordPress 6.0+, JSON-RPC for the in-plugin MCP server, REST endpoints for chat proxying and corpus sync. The visitor widget is ~30KB vanilla JS (no React/Vue runtime). Plugin size is ~350KB packaged.
How are API keys stored on the WordPress side?
AES-256-CBC encryption with the key derived from wp_salt('auth'). Stored in wp_options as animam_settings.api_key_enc. Decrypted only when needed (chat proxy, plan heartbeat, MCP signing). Never logged in plain text.
Can I extend the plugin with custom admin tools?
Yes via WordPress filters: animam_mcp_tools_register lets you register additional tool definitions; animam_mcp_tool_call_{name} executes the body. Tools are auto-listed in tools/list and respect the same JWT capability gating as native tools.
How does corpus sync handle large sites with 10k+ posts?
Initial sync uses POST /corpus/bulk with 25 entries per batch. Incremental updates run on save_post / delete_post hooks (idempotent externalId wp-{type}-{id}). For sites over 5k posts, run wp animam corpus resync in batches via WP-CLI.
Is the source code auditable?
The plugin source is open during evaluation (you receive the .zip and can inspect every line). Production releases are signed and shipped via Plugin Update Checker. The Animam API server is closed-source but ships SOC 2-style controls (audit log, PII scrubbing, signed webhooks).
How do I integrate Animam with my existing CRM (HubSpot, Pipedrive)?
Three options: (1) configure the WPForms bridge — agent submits the form, your existing WPForms entries fire your existing automations untouched. (2) configure outgoing webhooks at /tenants/:slug/webhooks — Animam ships submission events from voice / API / standalone form channels as Stripe-style HMAC-signed deliveries. (3) Use the MCP tool wp_rest_call to push directly from the agent during the conversation.