Ext Ops Panel
Open dashboard
Comparison

ai-integration-architect vs Aiqbee Brain

ai-integration-architect is a plugin bundle for AI coding tools published by pfbarros2. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Aiqbee Brain is an MCP server published by aiqbee.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceai-integration-architectAiqbee Brain
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 2
Stars (GitHub): 7
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

ai-integration-architect vs Aiqbee Brain
Factai-integration-architectAiqbee Brain
Marketplaces that list it11
Stars (GitHub)77
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.aiqbee.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pfbarros2/ai-integration-architect-plugingithub.com/aiqbee/aiqbee-ai
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 12 h ago, requires a key

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

ai-integration-architect

In its own words, on Claude Code: claude-plugins-community:

A Claude skill that helps teams plan, design, and scaffold AI integration into enterprise systems. 46% of enterprises say integrating AI into existing systems is their #1 challenge. This skill acts as a senior integration architect — it assesses your system landscape, recommends architecture patterns, generates production-ready code scaffolds, and produces deployment plans with security baked in.

Aiqbee Brain

In its own words, on Official MCP Registry:

AI knowledge graph for architecture, portfolio, and digital strategy management.

How to run each

ai-integration-architect As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ai-integration-architect@claude-community

Aiqbee Brain As a remote MCP server

Claude Code
claude mcp add --transport http brain https://mcp.aiqbee.com/mcp

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

Only Aiqbee Brain 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: ai-integration-architect · What it can do: Aiqbee Brain · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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