Ext Ops Panel
Open dashboard
Comparison

n8n vs io.github.chinlee2200-dotcom/bridgecore

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 3 (Docker MCP Catalog, npm registry (MCP servers), Community GitHub marketplaces). io.github.chinlee2200-dotcom/bridgecore is an MCP server published by chinlee2200-dotcom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplacen8nio.github.chinlee2200-dotcom/bridgecore
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 683
Pulls (Docker Hub): 163 637
Stars (Docker Hub): 24
Stars (GitHub): 23 228
Not marked · First seen
Not listed
npm registry (MCP servers) Listed
Version: 2.102.0
Downloads/month (npm): 298 715
Downloads/week (npm): 83 221
Forks (GitHub): 3 683
Stars (GitHub): 23 228
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.2
No figure published
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

n8n vs io.github.chinlee2200-dotcom/bridgecore
Factn8nio.github.chinlee2200-dotcom/bridgecore
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)23 228No figure on GitHub
Pulls (Docker Hub) (differs)163 637No figure on Docker Hub
Forks (GitHub) (differs)3 683No figure on GitHub
Last release (differs)2026-11-09 (better)2026-10-16 (worse)
Where it runs (differs)On your machine (mcp/n8n)Remote server (mcp.usebridgecore.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)42Not published
Environment variables it asks for (differs)5, secrets among them: 1Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/chinlee2200-dotcom/laboratory-
Changes in the last 7 days (differs)50
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 405

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

n8n

In its own words, on Docker MCP Catalog:

Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.

io.github.chinlee2200-dotcom/bridgecore

In its own words, on Official MCP Registry:

Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.

How to run each

n8n As a local MCP server: Docker image

Claude Code
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --transport stdio n8n -- docker run -i --rm -e N8N_API_KEY mcp/n8n

Requires: N8N_API_KEY (secret)

io.github.chinlee2200-dotcom/bridgecore As a remote MCP server

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

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

Only io.github.chinlee2200-dotcom/bridgecore has a remote endpoint we check. How we check endpoints

Tools each declares

Only n8n has

  • get_database_statistics
  • get_node_as_tool_info
  • get_node_documentation
  • get_node_essentials
  • get_node_info
  • get_property_dependencies
  • get_template
  • get_templates_for_task
  • list_ai_tools
  • list_node_templates
  • list_nodes
  • list_tasks
Show the remaining 30
  • list_templates
  • n8n_autofix_workflow
  • n8n_create_workflow
  • n8n_delete_execution
  • n8n_delete_workflow
  • n8n_diagnostic
  • n8n_get_execution
  • n8n_get_workflow
  • n8n_get_workflow_details
  • n8n_get_workflow_minimal
  • n8n_get_workflow_structure
  • n8n_health_check
  • n8n_list_available_tools
  • n8n_list_executions
  • n8n_list_workflows
  • n8n_trigger_webhook_workflow
  • n8n_update_full_workflow
  • n8n_update_partial_workflow
  • n8n_validate_workflow
  • n8n_workflow_versions
  • search_node_properties
  • search_nodes
  • search_templates
  • search_templates_by_metadata
  • tools_documentation
  • validate_node_minimal
  • validate_node_operation
  • validate_workflow
  • validate_workflow_connections
  • validate_workflow_expressions

Only io.github.chinlee2200-dotcom/bridgecore has

  • do
  • find_recipe
  • inspect_workflow
  • make_n8n_workflow
  • plan_automation

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.chinlee2200-dotcom/bridgecore as of 2026-10-20). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of io.github.chinlee2200-dotcom/bridgecore publish no settings it asks for, so we do not compare settings.

What it can do: n8n · What it can do: io.github.chinlee2200-dotcom/bridgecore · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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