xenition vs BridgeAI
xenition is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
xenition is a plugin bundle for AI coding tools published by Xenition. No marketplace we read lists it any more. BridgeAI is an MCP server published by bridgeaibrasil.com.br. 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 |  BridgeAI | |
|---|---|---|
| Community marketplace xenition/xenition-mcp | Removed on 2026-10-15 Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 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
| Fact | xenitionno longer listed · | BridgeAI |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.xenition.com/mcp) | Remote server (mcp.bridgeaibrasil.com.br/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/xenition/xenition-mcp | github.com/marcoshenriquemaia/bridgeai-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (3 days ago) |
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 xenition
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Turn a thread, skill, spreadsheet, or Claude/ChatGPT project into a visual Agent-Native app. Local code agents build, run, and screenshot-review it; Claude and ChatGPT on the web…
-
creatio-ai-app-development-toolkit
Creatio AI App Development Toolkit for business-plan driven Creatio app creation.
-
mcp io.github.seldonframe/mcp
Build, deploy, and sell AI agents for local-service businesses - from your IDE.
-
StoriesOnBoard - structured specifications for AI Agents
Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.
-
52 skills, 2 agents for AI-driven startup creation
-
Agentic Engineering toolkit with 12 structured workflow skills, 5 specialist agent personas, and 7 slash commands. Covers the full development lifecycle from idea to production…
What each says it does
xenition
Your Xenition workspace, app builder, automations and Studio in the chat.
BridgeAI
Hospedagem no Brasil que o agente opera: cria banco, publica, lê log e diz o custo.
How to run each
xenition
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BridgeAI As a remote MCP server
claude mcp add --transport http bridgeai https://mcp.bridgeaibrasil.com.br/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only BridgeAI 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: xenition · What it can do: BridgeAI · 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.