context-engineering vs Elicitly
context-engineering is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
context-engineering is a plugin bundle for AI coding tools published by Andrew Novykov. No marketplace we read lists it any more. Elicitly is an MCP server published by elicitly.ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Elicitly | |
|---|---|---|
| Community marketplace endorphin-ai/hasbrains-agent-kit | Removed on 2026-10-24 Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.6 Downloads/month (npm): 1 290 Downloads/week (npm): 221 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.8.6 Downloads/month (npm): 1 290 Downloads/week (npm): 221 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | context-engineeringno longer listed · | Elicitly |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 9 | 1 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release (differs) | Not published | 2026-11-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (elicitly) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/endorphin-ai/hasbrains-agent-kit | github.com/elicitly/elicitly |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-17 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of context-engineering
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Mission Planner, Agent Creator, Skill Creator, and Librarian — the complete Forge suite for science-backed AI team assembly
-
Put Claude Code and your other harnesses on one durable board: atomic claims and leases, live Mission Control, cost attribution, tamper-evident audit and shared memory
-
Skills for using AI itself well — picking the right tool, delegating to it, briefing it with context, designing AI workflows, verifying its output, and catching its mistakes.
-
A Codex meta-skill that designs domain-specific agent teams and reusable skills with bounded parallel orchestration.
-
AI model invocation, multi-agent orchestration, prompt distillation, and structured reasoning frameworks.
-
Commands and skills for writing and refining commands, hooks, skills for Claude Code, includes Anthropic Best Practices and Agent Persuasion Principles that can be useful for…
What each says it does
context-engineering
Context engineering for AI agents — AI-optimized second-brain skills, durable pipeline state for multi-agent handoffs, and expert prompt building.
Elicitly
Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor
How to run each
context-engineering
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Elicitly As a local MCP server: npm package
claude mcp add --transport stdio elicitly -- npx -y elicitlyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: context-engineering · What it can do: Elicitly · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.