GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Descripción del creador (original en inglés)
Unofficial MCP server for Make.com automation - build, validate & deploy scenarios via AI
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL, LOG_LEVELLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"make": {
"command": "npx",
"args": [
"-y",
"make-mcp-server"
],
"env": {
"MAKE_API_KEY": "your-value",
"MAKE_TEAM_ID": "your-value",
"MAKE_API_URL": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add make --env MAKE_API_KEY=your-value --env MAKE_TEAM_ID=your-value --env MAKE_API_URL=your-value --env LOG_LEVEL=your-value -- npx -y make-mcp-serverCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"make": {
"command": "npx",
"args": [
"-y",
"make-mcp-server"
],
"env": {
"MAKE_API_KEY": "your-value",
"MAKE_TEAM_ID": "your-value",
"MAKE_API_URL": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"make": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"make-mcp-server"
],
"env": {
"MAKE_API_KEY": "your-value",
"MAKE_TEAM_ID": "your-value",
"MAKE_API_URL": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
MAKE_TEAM_ID envMAKE_API_URL envLOG_LEVEL envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub danishashko, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: MAKE_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.3.3) llegó al registro hace 9 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: GitHub, Desktop Commander, Cloudflare MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
⚠️ Disclaimer: This is an unofficial, community-driven project created by a passionate fan of Make.com. It is NOT affiliated with, endorsed by, or officially supported by Make.com.
A Model Context Protocol (MCP) server that gives AI assistants like Claude, GitHub Copilot, and Cursor full access to Make.com module documentation, scenario validation, and one-click deployment. Search 200+ automation modules across 40+ apps, build blueprints with auto-healing, and deploy directly to Make.com — all from your AI chat.
metadata, adds designer coordinates, strips unsupported properties like router filterbuiltin:BasicRouter with multiple routes and recursive validationThe fastest way to get started — no cloning, no building:
Prerequisites: Node.js installed on your system
# Run directly — no installation needed!
npx -y make-mcp-server
The package includes a pre-built database with all 200+ Make.com modules. Just add it to your MCP client config and go.
Claude Desktop config (claude_desktop_config.json):
Basic configuration (documentation tools only):
{
"mcpServers": { "make-mcp-server": { "command": "npx", "args": ["-y", "make-mcp-server"], "env": { "LOG_LEVEL": "error" } } } }
Full configuration (with Make.com deployment):
{
"mcpServers": { "make-mcp-server": { "command": "npx", "args": ["-y", "make-mcp-server"], "env": { "LOG_LEVEL": "error", "MAKE_API_KEY": "your_api_key_here", "MAKE_TEAM_ID": "your_team_id", "MAKE_API_URL": "https://eu1.make.com/api/v2" } } } }
Note: npx will download and cache the latest version automatically. The package includes a pre-built database with all Make.com module information — no setup required.
Prerequisites: Docker installed on your system
# Build the Docker image
docker build -t make-mcp-server .
echo '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}},"id":1}' | docker run -i --rm make-mcp-server
Claude Desktop config:
Basic configuration (documentation tools only):
{
"mcpServers": { "make-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "--init", "-e", "LOG_LEVEL=error", "make-mcp-server" ] } } }
Full configuration (with Make.com deployment):
{
"mcpServers": { "make-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "--init", "-e", "LOG_LEVEL=error", "-e", "MAKE_API_KEY=your_api_key_here", "-e", "MAKE_TEAM_ID=your_team_id", "-e", "MAKE_API_URL=https://eu1.make.com/api/v2", "make-mcp-server" ] } } }
Important: The
-iflag is required for MCP stdio communication.
Prerequisites: Node.js and Git
# 1. Clone and install
git clone https://github.com/danishashko/make-mcp.git cd make-mcp npm install
npm run build
npm run scrape:prod
npm start
Claude Desktop config:
{
"mcpServers": { "make-mcp-server": { "command": "node", "args": ["/absolute/path/to/make-mcp/dist/mcp/server.js"], "env": { "LOG_LEVEL": "error", "MAKE_API_KEY": "your_api_key_here", "MAKE_TEAM_ID": "your_team_id" } } } }
Note: The Make.com API credentials are optional. Without them, you'll have access to all documentation, search, and validation tools. With them, you'll additionally get scenario deployment capabilities.
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Restart Claude Desktop after updating configuration.
make-mcp-server works with any MCP-compatible client:
.vscode/mcp.jsonclaude mcp add commandThen ask your AI assistant things like:
"Create a Make scenario that watches a Slack channel for new messages and logs them to a Google Sheet"
"What modules does Make have for sending emails?"
"Validate this scenario blueprint..."
Tip: The AI will automatically call tools_documentation first to understand how to use the server effectively.
| Tool | Description |
|---|---|
tools_documentation | START HERE — Returns comprehensive documentation for all tools, prompts, and resources |
search_modules | Full-text search across 200+ Make.com modules |
get_module | Get detailed module info with parameters and docs |
check_account_compatibility | Check if modules are available in your current Make account/region (with suggestions) |
validate_scenario | Validate a scenario blueprint before deployment |
create_scenario | Deploy a scenario to Make.com via API |
search_templates | Search reusable scenario templates |
list_apps | List all apps with module counts |
The create_scenario tool automatically fixes common issues in LLM-generated blueprints:
| Issue | Auto-Fix |
|---|---|
Missing metadata section | Injects full metadata with version, scenario config, and designer |
Missing metadata.designer on modules | Adds { x: 0, y: 0 } coordinates |
Router filter in route objects | Strips unsupported filter property (configure filters in Make.com UI) |
Missing version on modules | Left unset — Make.com auto-resolves the latest installed version |
Catalog mismatch (IM007, module not available) | Checks live modules in your account/region, auto-remaps close matches, retries deploy once |
Tip: Do NOT hardcode
"version": 1on modules. Some apps (e.g., HTTP) are on v4+ and specifying the wrong version causes "Module not found" errors.
| Prompt | Description |
|---|---|
build_scenario | Guided workflow for creating a Make.com scenario from a natural language description |
explain_module | Get a detailed explanation of any Make.com module with usage examples |
| Resource URI | Description |
|---|---|
make://apps | List of all available apps with module counts |
make-mcp-server # Start the MCP server (stdio transport)
make-mcp-server --scrape # Populate/refresh the module database make-mcp-server --version # Print version make-mcp-server --help # Show help
| Variable | Required | Default | Description |
|---|---|---|---|
MAKE_API_KEY | For deployment | — | Make.com API key |
MAKE_API_URL | No | https://eu1.make.com/api/v2 | Make.com API base URL |
MAKE_TEAM_ID | For deployment | — | Default team ID for scenario deployment |
DATABASE_PATH | No | /data/make-modules.db | SQLite database file path |
LOG_LEVEL | No | info | Logging level: debug, info, warn, error, silent |
MAKE_MODULE_CACHE_TTL_MS | No | 300000 | Cache TTL for live module catalog checks (milliseconds) |
npm run build # Compile TypeScript + copy schema + add shebang
npm run build:tsc # TypeScript only (no packaging) npm run start:dev # Start with tsx (no build needed) npm run dev # Start with file watching npm run scrape # Populate DB with tsx (dev) npm run scrape:prod # Populate DB from compiled JS npm run smoke:compat # One-command account compatibility + validation smoke check npm test # Run all 43 tests npm run test:watch # Run tests in watch mode
npm run prepublishOnly # Build + populate DB + verify (runs automatically on npm publish)
npm publish # Publish to npm registry
The test suite includes 43 tests across 3 files:
npm test
Use this when you just changed validation/deploy logic and want confidence quickly:
# 1) Fast regression check
npm test
npm run smoke:compat
npm run start:dev
Then in your MCP client (Claude/Cursor/Copilot), run this sequence:
check_account_compatibility with a known module, e.g. gateway:CustomWebHookvalidate_scenario with your blueprintcreate_scenario only if compatibility is goodIf step 1 reports incompatible modules, use the suggested replacement IDs before deploying.
src/
├── mcp/ │ └── server.ts # MCP server with tools, prompts, resources ├── database/ │ ├── schema.sql # SQLite + FTS5 schema │ └── db.ts # Database access layer (npx-safe path resolution) ├── scrapers/ │ └── scrape-modules.ts # Module data population (224 modules) └── utils/ └── logger.ts # Structured stderr-only logger bin/ ├── make-mcp.js # CLI entry point (npx, --help, --version, --scrape) └── postinstall.js # Post-install verification scripts/ ├── build.js # Build: tsc + copy schema + add shebang ├── prepublish.js # Publish prep: build + populate DB + verify └── smoke-compat.js # Fast local smoke test for module compatibility + validation data/ └── make-modules.db # Pre-built SQLite database (bundled in npm package) tests/ ├── database.test.ts # Dat
Solo se muestra el principio; lee el resto en el repo