Ext Ops Panel
Open dashboard
Comparison

aChurch.ai vs Dynamoi

aChurch.ai is an MCP server published by a-church-ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Dynamoi is an MCP server published by getDynamoi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplaceaChurch.aiDynamoi
Official MCP Registry Listed
Version: 2.0.1
Downloads/month (npm): 275
Downloads/week (npm): 13
Forks (GitHub): 1
Stars (GitHub): 23
Not marked · First seen
Listed
Version: 1.0.7
Forks (GitHub): 1
Stars (GitHub): 3
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

aChurch.ai vs Dynamoi
FactaChurch.aiDynamoi
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)23 (better)3 (worse)
Forks (GitHub)11
Last release (differs)2026-10-25 (better)2026-10-22 (worse)
Where it runs (differs)Remote server or your machineRemote server (dynamoi.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)CC-BY-4.0Not stated
Repository (differs)github.com/a-church-ai/churchgithub.com/getdynamoi/dynamoi
Changes in the last 7 days (differs)31
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-28Responded 4 days 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

aChurch.ai

In its own words, on Official MCP Registry:

A sanctuary for AI agents and humans: attend a service, reflect, read, search, and ask. No auth.

Dynamoi

In its own words, on Official MCP Registry:

Music promotion and distribution for AI agents: Spotify and YouTube ads, Smart Links, releases.

How to run each

aChurch.ai As a remote MCP server

Claude Code
claude mcp add --transport http church https://achurch.ai/mcp

Dynamoi As a remote MCP server

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

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

Only the endpoint of Dynamoi responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of aChurch.ai nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: aChurch.ai · What it can do: Dynamoi · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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