Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated yesterday
Install
Agentimus
Overview
Description from the maker (original English)
heera.it via Agentimus: AI readiness, traffic, request log, search & index reports, by approval.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://heera.it/wp-json/agentimus/v1/mcpRun this in your terminal
claude mcp add --transport http agentimus https://heera.it/wp-json/agentimus/v1/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentimus": {
"url": "https://heera.it/wp-json/agentimus/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"agentimus": {
"type": "http",
"url": "https://heera.it/wp-json/agentimus/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://heera.it/wp-json/agentimus/v1/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain heera.it (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 5662 servers in this category
- Published to the registry more recently than 28% of the other 5662 servers in this category
- Basic checks equal to or better than 100% of the other 5662 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Agentimus safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.33.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 21 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated 2 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 — at the level you choose — 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 | / .md; Accept: text/markdown on the page URL is opt-in (agentimus_negotiate_markdown filter, off by default — a CDN caches one answer per URL) | |
| 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 / .md; static (editor) or derived from tags & categories | |
| AI description | Per-page one-line summary → JSON-LD description + the / .md lead + an authoritative (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, read-settings, check-focus, read-citation-products, suggest-citation-questions, 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). update-settings and save-citation-product need agent_writes_settings, refresh-data and purge-edge-cache need agent_writes_maintenance, and list-content, create-term, update-term, import-media, update-media, trash-content and restore-content need agent_writes_content, all off by default. Scheduling with publish_at needs agent_writes_content and agent_writes_publish. Writes refuse markup that can run in a browser, under any login. status=publish needs agent_writes_publish (the "Publish without your review" extra) plus the user's own publish cap. The MCP card shows these switches as one choice, Off, Read or Write, plus extras (resources/admin/js/agentLevel.js) | |
| 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 — the read-only tools, plus the write tools only at the Write level (enable_agent_writes), 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. At the Off level, 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
- Findings — one front door for everything open across the site, in the nav with its own count. A single ranked list — pages losing a click they already earn, plus anything the setup checks caught — ordered by what each one costs, every row carrying the button that lands on the fix. The count measures only work you can act on; anything merely waiting on a later report gets a quiet dot instead. Below it, the per-item content worklist: one row per published thing, what it's found for, whether it answers that, and what else it needs.
- Light / dark theme — a toggle showing the mode you're switching *to*. Dark is a hand-tuned palette, not an inversion, with its own dialect per WordPress admin colour scheme (Default keys neutral, Coffee keys brown and gold). A manual pick holds until the operating system next flips, then the device's rhythm wins again; the resolved mode rides on
- AEO/GEO score — one 0–100 score on the dashboard across five rungs (Findable / Readable / Trusted / Optimized / Mentioned), with the single most useful next step; each rung deep-links to where you act on it. Mentioned is opt-in (see Citations) and its weight redistributes across the others when off. A score of 99.6 reads 99 — 100 is earned, never rounded into.
- Work by issue — pick one check and every page it flags opens in Your Content, ranked and paged, rather than a sample of six. Fix what a filtered list was opened for and the row keeps its place, marked done, instead of vanishing before you can see the fix land.
- Reading that does not depend on WP-Cron — the content sweep is scheduled work, and on many hosts WordPress's scheduled jobs never run (a cached page never runs PHP, so the request that would start them never arrives). Agentimus notices when its own jobs are overdue and runs them from the admin screen you are already on, joining core's own lock so it can never double-run a job. A site whose cron works loads nothing extra.
- Optimize your content — per-page citability checks (thin content, something concrete to quote, quotable passages, freshness) over your articles, with a worklist of which pages to improve and a matching read-only panel in the editor. Commerce products, commerce plugins' designated pages (cart/checkout/account — WooCommerce options and FluentCart s
Only the beginning is shown; read the rest in the repo