architecture vs Agent-Native Plan
architecture is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
architecture is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Agent-Native Plan is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  Agent-Native Plan | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.4.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.4.2 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 688 Stars (GitHub): 7 515 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 | architectureno longer listed · | Agent-Native Plan |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 7 515 |
| Forks (GitHub) (differs) | 5 | 688 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (plan.agent-native.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/builderio/agent-native |
| Changes in the last 7 days (differs) | 6 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
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 architecture
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Collaborative technical discussion with proactive requirements gathering
-
System architecture agents, design patterns, and architectural decision support
-
Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.
-
Cognitive brainstorming protocol: GROUND -> EXPLORE -> DECIDE -> STRESS -> SHIP. Includes domain skills for technical architecture and conceptual work.
-
For easy problems, start here. For harder problems, do this after Explore.
-
Multi-perspective plan review with VP Product, VP Engineering, and VP Design for implementation plans and architecture proposals.
What each says it does
architecture
Decides the engineering approach for an intent in an interactive session: investigates, proposes two or three genuinely different approaches with trade-offs, recommends, lets the user decide, and writes the decision doc. Not a task-by-task plan; use cut-it. Not a multi-perspective debate; use design-council. Not product intent; use product-intent. Not a typed implementation handoff; use tech-spec.
Agent-Native Plan
Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing
How to run each
architecture
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Agent-Native Plan As a remote MCP server
claude mcp add --transport http agent-native-plan https://plan.agent-native.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Agent-Native Plan has a remote endpoint we check. How we check endpoints
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: architecture · What it can do: Agent-Native Plan · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.