Ext Ops Panel
Open dashboard
Comparison

Camunda BPM Process Engine vs freee-mcp

Camunda BPM Process Engine is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). freee-mcp is a plugin bundle for AI coding tools published by freee. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplaceCamunda BPM Process Enginefreee-mcp
Docker MCP Catalog Listed
Version: sha256:fbea3848bcb6
Forks (GitHub): 5
Pulls (Docker Hub): 57 591
Stars (Docker Hub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Community marketplace freee/freee-mcp Not listed Listed
Version: 0.37.1
Forks (GitHub): 58
Stars (GitHub): 508
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

Camunda BPM Process Engine vs freee-mcp
FactCamunda BPM Process Enginefreee-mcp
Marketplaces that list it11
Stars (GitHub) (differs)14 (worse)508 (better)
Pulls (Docker Hub) (differs)57 591No figure on Docker Hub
Forks (GitHub) (differs)5 (worse)58 (better)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/camunda)Remote server (mcp.freee.co.jp/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/lepoco/mcp-camundagithub.com/freee/freee-mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Camunda BPM Process Engine

In its own words, on Docker MCP Catalog:

Tools to interact with the Camunda 7 Community Edition Engine using the Model Context Protocol (MCP). Whether you're automating workflows, querying process instances, or integrating with external systems, Camunda MCP Server is your agentic solution for seamless interaction with Camunda.

freee-mcp

In its own words, on Community GitHub marketplaces:

freee API を MCP 経由で操作するためのスキル。詳細なAPIリファレンス(パラメータ、リクエストボディ、レスポンス情報含む)と、freee-mcp を使用した API 呼び出しガイドを提供。OAuth 認証とトークン管理を自動化し、経費申請、会計データ取得、人事情報管理など、freee の様々な機能を利用可能。

How to run each

Camunda BPM Process Engine As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio camunda -- docker run -i --rm mcp/camunda

freee-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add freee/freee-mcp
/plugin install freee-mcp@freee-mcp-marketplace

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

Tools each declares

The marketplaces of freee-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Camunda BPM Process Engine · What it can do: freee-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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