Ext Ops Panel
Open dashboard
Comparison

thinkfu vs aChurch.ai

thinkfu is a plugin bundle for AI coding tools published by move38studios. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-16. 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
MarketplacethinkfuaChurch.ai
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 4
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.0
Downloads/month (npm): 262
Downloads/week (npm): 48
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

thinkfu vs aChurch.ai
FactthinkfuaChurch.ai
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (worse)23 (better)
Forks (GitHub) (differs)4 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle33
Licence (differs)PolyForm-Small-Business-1.0.0CC-BY-4.0
Repository (differs)github.com/move38studios/thinkfugithub.com/a-church-ai/church
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 30 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

thinkfu

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

Metacognition as a service. Creative thinking moves for AI agents — plan, explore, unstick, and evaluate using 200+ curated techniques for lateral thinking.

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

thinkfu As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install thinkfu@claude-community

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.

Only aChurch.ai 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

Only thinkfu asks for

  • THINKFU_NODE_MODULES

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: thinkfu · What it can do: aChurch.ai · 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. 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