Ext Ops Panel
Open dashboard
Comparison

AIquila — Nextcloud MCP Server vs CloudBridge

AIquila — Nextcloud MCP Server is an MCP server published by elgorro. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). CloudBridge is an MCP server published by cloud-bridge.ru. 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
MarketplaceAIquila — Nextcloud MCP ServerCloudBridge
Official MCP Registry Listed
Version: 0.5.3
Downloads/month (npm): 1 601
Downloads/week (npm): 748
Forks (GitHub): 17
Stars (GitHub): 39
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.5.3
Downloads/month (npm): 1 601
Downloads/week (npm): 748
Forks (GitHub): 17
Stars (GitHub): 39
Not marked · First seen
Not listed

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

AIquila — Nextcloud MCP Server vs CloudBridge
FactAIquila — Nextcloud MCP ServerCloudBridge
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)39No figure on GitHub
Forks (GitHub) (differs)17No figure on GitHub
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (aiquila-mcp)Remote server (cloud-bridge.ru/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/elgorro/aiquilaNot stated
Changes in the last 7 days (differs)52
First seen (differs)2026-10-112026-11-03
Endpoint at the last check (differs)no remote endpoint we checkResponded 28 h ago

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

AIquila — Nextcloud MCP Server

In its own words, on Official MCP Registry:

Nextcloud MCP server — 349 tools: files, calendar, contacts, mail, Talk, Deck, photos, maps, notes

CloudBridge

In its own words, on Official MCP Registry:

Transfer and sync files between 19 cloud storages (Yandex, Google, VK, Telegram, S3)

How to run each

AIquila — Nextcloud MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: NEXTCLOUD_PASSWORD (secret), NEXTCLOUD_URL, NEXTCLOUD_USER

CloudBridge As a remote MCP server

Claude Code
claude mcp add --transport http cloudbridge https://cloud-bridge.ru/api/mcp --header "X-API-Key: <YOUR_CLOUDBRIDGE_API_KEY>"

Requires: X-API-Key header

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

Only CloudBridge 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

The marketplaces of CloudBridge publish no settings it asks for, so we do not compare settings.

What it can do: AIquila — Nextcloud MCP Server · What it can do: CloudBridge · Compare two other plugins

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.

Where the data comes from: how the catalog is built