heera.it via Agentimus: AI readiness, traffic, request log, search & index reports, by approval.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
Agentimus
Two things for the age of AI agents. (1) Make any WordPress site legible and citable —
llms.txt, a full-text edition, markdown delivery, JSON-LD, content-signal robots rules —
then score how AEO/GEO-ready it is and what to fix next. (2) Let the AI tools you already
use operate the site over MCP: a Model Context Protocol server ships inside the plugin, so
Claude Code, Claude Desktop, Cursor or Codex can read your readiness/traffic/bot data and —
behind two more opt-in switches — draft, edit and publish posts and pages, each write running
as the signed-in user, permission-checked and audited. Lightweight, no SEO bloat, no framework.
Live on WordPress.org: https://wordpress.org/plugins/agentimus/
📖 Documentation: https://heera.github.io/agentimus/ — full user manual and developer reference.
Install
- From your dashboard — Plugins → Add New → search "Agentimus" → Install → Activate.
- From WordPress.org — https://wordpress.org/plugins/agentimus/.
- From source — clone this repo, run
npm install && npm run build(producesassets/admin/), then copy or symlink the folder intowp-content/plugins/.
What it does
| Signal | Endpoint / output |
|---|---|
| Link index | /llms.txt |
| Full-text edition | /llms-full.txt |
| Markdown delivery | /<slug>.md or Accept: text/markdown |
| Structured data | JSON-LD WebSite + Person/Organization + BlogPosting + BreadcrumbList (defers to SEO plugins) |
| Topics for AI | Per-page topics → JSON-LD keywords + about DefinedTerm entities (with optional Wikidata sameAs via the agentimus_topic_links filter) + a Topics: line in /<slug>.md; static (editor) or derived from tags & categories |
| AI description | Per-page one-line summary → JSON-LD description + the /<slug>.md lead + an authoritative <meta name="description"> (replaces the theme's, defers to an SEO plugin); editor-set, falling back to the excerpt or a ~30-word content summary. A settings sub-toggle can limit it to the JSON-LD + .md surfaces only |
| Writing assistant (opt-in) | The quill button on every Agentimus screen opens a drawer: brief → editable outline → the article writes every section in parallel (/assistant/compose-section per part + one dressing call; long posts aren't capped by a single response, a failed part retries alone, and a mid-write reload resumes) → full preview (title, real blocks, AI description, topics, suggested categories/tags, draft/pending choice) → Create draft lands straight in the editor. Drafts are written to the same bar the Readability panel grades — a liftable opening summary, quotable paragraph lengths, plain sentences, cited sources (readability_rules(), its paragraph cap derived from PageCheck's own threshold). Creation only: a drafted post opens in the editor, where revision lives (the drawer's old edit path and its safe-block gate are gone — that gate existed because a drawer can only handle blocks it wrote itself, and declining real posts was the wrong answer to the right problem). Shapes are per type: Assistant::shape_for() writes a hierarchical type as a PAGE — no invented sections, no image slots, no taxonomy, [placeholder] where only the owner knows a fact — and MCP creation runs the same prompts. Images arrive as alt-filled placeholder blocks: Generate image from the alt text on every image block, a Featured image (AI) sidebar panel, and Ask AI at three scopes — one block, a multi-block selection (BlockSettingsMenuControls, since InspectorControls never renders during multi-select), or a document planner that returns an outline-scoped edit list applied one at a time against a re-read anchor map (replaceBlocks mints new clientIds, so stale ids silently no-op). Server-side it's the same audited write path as MCP (Assistant.php → ContentWriter), gated by enable_agent_writes + the user's own caps, with every generation routed through Assist::generate() (rate-limited, Content-Guidelines-aware) and status clamped to draft|pending — the assistant can never publish |
| Write with AI (opt-in) | Editor "Draft with AI" writes the AI description and "Suggest with AI" fills Topics, both from the page's own content; "Fix with AI" drafts a fix per AI-Readability warning (opening summary inserts in one click, the rest copy-only). Routes through the WordPress 7.0 AI Client — your own provider key, never handled by the plugin; hidden until a provider is configured under Settings → Connectors |
| AI abilities | Two tiers via wp_register_ability, each ability permission-gated like its source screen. Read (always registered): agentimus/read-readiness, read-findings (the Findings screen's own ranked front door, bounded at 12 rows), read-audience (people and machines counted apart, never summed), read-ai-visibility, read-ai-traffic, read-request-log, read-edge-traffic, read-search-visibility, read-search-performance, read-search-opportunities, read-google-index (optional url answers from stored checks, no quota), identify-bot, read-content-issues (which pages need work, what each is flagged for, and how old that verdict is — the list read-findings summarises), read-terms (the categories and tags this site already uses, by the exact names the write tools expect), check-page, preview-schema/-markdown, scan-exposed-files, suggest-internal-links, search-media (title + _wp_attachment_image_alt, gated on upload_files). Write (registered only while enable_agent_writes is on — off by default, requires the MCP server switch, and off means the abilities don't exist on any surface): create-content/update-content (draft-first; categories & tags by name with wp-admin's own creation rules, featured image by attachment ID or sideloaded URL, AI description/topics in the same call), write-description, write-topics, write-search-fields (the focus keyword and the SEO title — the two fields that decide how a page appears in a search result, and the last two an agent could not reach), and apply-fix (enacts a readiness check's own remediation from a closed vocabulary that can only enable documented features). status=publish needs a third switch (agent_writes_publish) plus the user's own publish cap |
| MCP server (opt-in) | /wp-json/agentimus/v1/mcp — the WordPress MCP Adapter ships inside the plugin (Composer-vendored, Jetpack-autoloader arbitrated) behind the enable_mcp_server switch (Settings → Discovery, off by default; WP 6.9+). External MCP clients (Claude Code, Claude Desktop, Codex) authenticate with an application password and get exactly the abilities above — twenty read-only tools, plus the six write tools only while the write switch is on, and four resources (llms.txt, llms-full.txt, discovery.json, the agent card) declared with meta.mcp.uri; a resource whose endpoint is switched off is never registered (the server's self-description says which tier it's running) — the adapter's generic execute-any-ability default server stays suppressed, every call is audited in Agent Access, and toggling off hard-disconnects live clients. With the switch off, the library is never loaded and no endpoint exists |
| XML sitemap | /agentimus-sitemap.xml — opt-in fallback, generated only when neither WordPress core nor an SEO plugin already provides one (sitemap index + paginated sub-sitemaps) |
| Crawler policy | robots.txt content-signal + training-crawler blocklist |
| Discovery layer | /.well-known/discovery.json (+ agent-card.json, mcp.json) |
| Change feed | /agentimus-changes.json?since= — recently added, updated and removed content as JSON, so an agent fetches only the delta (advertised in discovery.json; on by default) |
| Crawl enforcement (opt-in) | hard-block (403) denylisted, spoofed-"scanner", or proven-impostor user-agents at the generated endpoints — ACME-safe, off by default; optional bot-identity verification (forward-confirmed reverse DNS + operators' published IP ranges, via an owner-editable Verified-bots registry) so a spoofed bot name can't earn the allowlist and a proven fake is refused |
In the admin
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Agentimus
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/agentimus)HTML Embed
<a href="https://allmcps.com/mcp/agentimus"><img src="https://allmcps.com/api/badge/agentimus?style=directory" alt="Agentimus on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
27Quality signal: Emerging · 27/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.