Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Make MCPCodebase Memory MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Make MCPShortlist candidate	Codebase Memory MCPMCP100 Recommended
Task fit
Best for	Run and manage Make automation workflows from MCP clients Run and manage Make automation workflows from MCP clients.	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Management scopes can modify scenarios, connections, webhooks, data stores and organization resources; scenario runs can trigger downstream external actions. OAuth can restrict access to a specific Make organization, while MCP-token access is broader by token scope.	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	Management scopes can modify scenarios, connections, webhooks, data stores and organization resources; scenario runs can trigger downstream external actions. OAuth can restrict access to a specific Make organization, while MCP-token access is broader by token scope.	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP Make · Publisher source ↗	First-party MCP DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	Not documented	44,904 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	No reliable download data	28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z
External adoption evidence	Not documented	npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	OAuth to `https://mcp.make.com`, or an MCP token using the Make-hosted regional connection URL.	local stdio; no remote auth needed
Cost	No separate MCP-server price was stated in the reviewed MCP overview. Scenario-run tools are available across plans; management-tool availability is plan-dependent.	none beyond local resources
Permissions	Available tools are controlled by granted OAuth/MCP-token scopes and the selected Make organization. Scenario-run tools are broadly available; management tools depend on plan and granted management scopes.	reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handling	Tool inputs are sent to Make to invoke or manage Make resources/scenarios, and Make returns tool outputs to the MCP client. The reviewed MCP docs do not state a separate MCP-specific model-training policy.	local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs	Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed. Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk context	Running a scenario can trigger downstream external actions. Management scopes can modify Make scenarios, connections, webhooks, data stores, and organization resources.	latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review	2026-10-19	2026-09-23
Candidate evidence	2026-10-20	2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →