Make vs devmcp
Make is an MCP server published by integromat. Marketplaces we read that list it: 1 (Official MCP Registry). devmcp is an MCP server published by rudranaresh0201. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
| Marketplace |  Make |  devmcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Forks (GitHub): 39 Stars (GitHub): 137 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (PyPI): 85 Downloads/week (PyPI): 36 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | Make | devmcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 137 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 39 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.make.com/v2) | On your machine (devmcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/integromat/make-skills | github.com/rudranaresh0201/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | no 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
Make
Build, run and debug Make automation scenarios.
devmcp
Git/CI MCP server with the full protocol surface (tools, resources, prompts, roots, sampling).
How to run each
Make As a remote MCP server
claude mcp add --transport http make https://mcp.make.com/v2devmcp As a local MCP server: PyPI package
claude mcp add --transport stdio devmcp -- uvx devmcp-server --repo-path "<YOUR_REPO_PATH>"Requires: --repo-path
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Make 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Make · What it can do: devmcp · 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.