Ext Ops Panel
Open dashboard
Comparison

AiNecto vs Enterprise Architect

AiNecto is an MCP server published by codelives. Marketplaces we read that list it: 1 (Official MCP Registry). Enterprise Architect is an MCP server published by mm6502. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAiNectoEnterprise Architect
Official MCP Registry Listed, marked deprecated
Version: 0.8.1
Downloads/month (npm): 2 380
Downloads/week (npm): 1 149
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 3.0.0
Downloads/month (npm): 270
Downloads/week (npm): 101
Forks (GitHub): 2
Stars (GitHub): 0
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

AiNecto vs Enterprise Architect
FactAiNectoEnterprise Architect
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)1 (worse)2 (better)
Last release (differs)2026-11-07Not published
Where it runs (differs)Remote server or your machineOn your machine (enterprise-architect-mcp)
Transport (differs)stdio, Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/codelives/ainectogithub.com/mm6502/enterprise-architect-mcp
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 24 h ago, requires authenticationno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AiNecto

In its own words, on Official MCP Registry:

AiNecto MCP connector for workspace, document, ERD, diagram, task, and attachment workflows.

Enterprise Architect

In its own words, on Official MCP Registry:

Read-only search and navigation of Sparx Enterprise Architect .qea model exports

How to run each

AiNecto As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ainecto -- npx -y @ainecto/mcp

Enterprise Architect As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio enterprise-architect-mcp -- npx -y enterprise-architect-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AiNecto 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: AiNecto · What it can do: Enterprise Architect · Compare two other plugins

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.

Where the data comes from: how the catalog is built