Ext Ops Panel
Open dashboard
Comparison

MidOS - MCP Community Library vs aChurch.ai

MidOS - MCP Community Library is an MCP server published by MidOSresearch. Marketplaces we read that list it: 1 (Official MCP Registry). aChurch.ai is an MCP server published by a-church-ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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
MarketplaceMidOS - MCP Community LibraryaChurch.ai
Official MCP Registry Listed
Version: 2026.2.27
Downloads/month (PyPI): 134
Downloads/week (PyPI): 26
Forks (GitHub): 5
Stars (GitHub): 7
Not marked · First seen
Listed
Version: 2.0.1
Downloads/month (npm): 275
Downloads/week (npm): 13
Forks (GitHub): 1
Stars (GitHub): 23
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

MidOS - MCP Community Library vs aChurch.ai
FactMidOS - MCP Community LibraryaChurch.ai
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (worse)23 (better)
Forks (GitHub) (differs)5 (better)1 (worse)
Last release (differs)Not published2026-10-25
Where it runsRemote server or your machineRemote server or your machine
Transport (differs)stdio, Streamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle3
Licence (differs)Not statedCC-BY-4.0
Repository (differs)github.com/midosresearch/midosgithub.com/a-church-ai/church
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-15Not responding since 2026-10-28

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

MidOS - MCP Community Library

In its own words, on Official MCP Registry:

Curated knowledge for AI agents — 19K chunks, 121 skills, semantic search via MCP

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.

How to run each

MidOS - MCP Community Library As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MIDOS_API_KEY=<YOUR_MIDOS_API_KEY>" --transport stdio midos -- uvx midos-mcp

Requires: MIDOS_API_KEY (secret)

aChurch.ai As a remote MCP server

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

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

Neither endpoint responded at the last daily 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

Only MidOS - MCP Community Library asks for

  • MIDOS_API_KEY (secret)

Only aChurch.ai asks for

  • ACHURCH_MCP_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: MidOS - MCP Community Library · What it can do: aChurch.ai · 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