Ext Ops Panel
Open dashboard
Comparison

com.furrowforms/furrow-forms vs io.github.mwbidwell/bionicforms-mcp

com.furrowforms/furrow-forms is an MCP server published by furrowforms.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mwbidwell/bionicforms-mcp is an MCP server published by mwbidwell. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacecom.furrowforms/furrow-formsio.github.mwbidwell/bionicforms-mcp
Official MCP Registry Listed
Version: 1.0.1
Downloads/month (npm): 157
Downloads/week (npm): 26
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed, marked deprecated
Version: 1.0.3
Downloads/month (npm): 147
Downloads/week (npm): 20
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

com.furrowforms/furrow-forms vs io.github.mwbidwell/bionicforms-mcp
Factcom.furrowforms/furrow-formsio.github.mwbidwell/bionicforms-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.furrowforms.com/mcp)On your machine (@bionicforms/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/useburrow/furrow-formsgithub.com/mwbidwell/form_builder
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 39 h ago, requires a keyno remote endpoint we check

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

com.furrowforms/furrow-forms

In its own words, on Official MCP Registry:

Form backend an agent runs end to end: provision forms, snippets, spam, signed webhooks.

io.github.mwbidwell/bionicforms-mcp

In its own words, on Official MCP Registry:

Build forms, manage responses, and run AI analysis via the BionicForms API.

How to run each

com.furrowforms/furrow-forms As a remote MCP server

Claude Code
claude mcp add --transport http furrow-forms https://api.furrowforms.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: FURROW_TOKEN (secret), Authorization header

io.github.mwbidwell/bionicforms-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "BIONICFORMS_API_KEY=<YOUR_BIONICFORMS_API_KEY>" --transport stdio bionicforms-mcp -- npx -y @bionicforms/mcp-server

Requires: BIONICFORMS_API_KEY (secret)

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

Only com.furrowforms/furrow-forms 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 com.furrowforms/furrow-forms asks for

  • FURROW_TOKEN (secret)

Only io.github.mwbidwell/bionicforms-mcp asks for

  • BIONICFORMS_API_KEY (secret)

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

What it can do: com.furrowforms/furrow-forms · What it can do: io.github.mwbidwell/bionicforms-mcp · Compare two other plugins

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.

Where the data comes from: how the catalog is built