Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
Inferido de los transportes que declara este listado (streamable-http). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.
La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.
Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo completo.
create_workflowCreate a BlinkBox automation workflow with fully configured nodes. REQUIREMENT: every node config must be production-ready — real field values, real prompts, real channel names, real cron expressions. No placeholders, no empty strings (except credentialId which users fill in). A workflow that needs…Create a BlinkBox automation workflow with fully configured nodes. REQUIREMENT: every node config must be production-ready — real field values, real prompts, real channel names, real cron expressions. No placeholders, no empty strings (except credentialId which users fill in). A workflow that needs…
No se publicó ningún esquema de entrada para esta herramienta.
ask_userAsk targeted clarifying questions when the request is genuinely ambiguous or when building an AI agent. AI-agent requests should use a 5-point build brief: goal, entrypoint, model/cost, memory, and credential/config readiness. Each question must have 3–5 clickable option chips. Call this ONLY ONCE…Ask targeted clarifying questions when the request is genuinely ambiguous or when building an AI agent. AI-agent requests should use a 5-point build brief: goal, entrypoint, model/cost, memory, and credential/config readiness. Each question must have 3–5 clickable option chips. Call this ONLY ONCE…
No se publicó ningún esquema de entrada para esta herramienta.
create_fileCreate a file and send it to the user as a download. Use this whenever producing code, documents, CSV/JSON data, reports, or any file the user would want to save.Create a file and send it to the user as a download. Use this whenever producing code, documents, CSV/JSON data, reports, or any file the user would want to save.
No se publicó ningún esquema de entrada para esta herramienta.
blinkboxSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
list_automationsList the user's Blinkbox automations (workflows) with their on/off status, trigger, and id.List the user's Blinkbox automations (workflows) with their on/off status, trigger, and id.
No se publicó ningún esquema de entrada para esta herramienta.
get_automationGet full details of one automation by name or id: status, trigger, and its steps.Get full details of one automation by name or id: status, trigger, and its steps.
No se publicó ningún esquema de entrada para esta herramienta.
run_automationRun an automation now by name or id (works whether it's active or not). Optionally pass input data. Returns the execution id.Run an automation now by name or id (works whether it's active or not). Optionally pass input data. Returns the execution id.
No se publicó ningún esquema de entrada para esta herramienta.
get_executionCheck the status and result of a workflow run by its execution id.Check the status and result of a workflow run by its execution id.
No se publicó ningún esquema de entrada para esta herramienta.
get_execution_logsGet the step-by-step logs for a workflow run by execution id.Get the step-by-step logs for a workflow run by execution id.
No se publicó ningún esquema de entrada para esta herramienta.
list_executionsList recent runs of an automation (by name or id) with their statuses.List recent runs of an automation (by name or id) with their statuses.
No se publicó ningún esquema de entrada para esta herramienta.
activate_automationTurn an automation ON (by name or id) so its trigger runs it automatically. The workflow is validated first; if it's incomplete this returns why.Turn an automation ON (by name or id) so its trigger runs it automatically. The workflow is validated first; if it's incomplete this returns why.
No se publicó ningún esquema de entrada para esta herramienta.
deactivate_automationTurn an automation OFF (by name or id) so it stops running automatically.Turn an automation OFF (by name or id) so it stops running automatically.
No se publicó ningún esquema de entrada para esta herramienta.
rename_automationprivilegiadaRename an automation (look it up by current name or id).Rename an automation (look it up by current name or id).
No se publicó ningún esquema de entrada para esta herramienta.
delete_automationprivilegiadaPermanently delete an automation by name or id. This cannot be undone.Permanently delete an automation by name or id. This cannot be undone.
No se publicó ningún esquema de entrada para esta herramienta.
list_nodesBrowse or search Blinkbox's node catalog — the building blocks of a workflow. Only nodes the user can actually reach from a picker are listed, so anything returned here is safe to build with.Browse or search Blinkbox's node catalog — the building blocks of a workflow. Only nodes the user can actually reach from a picker are listed, so anything returned here is safe to build with.
No se publicó ningún esquema de entrada para esta herramienta.
get_nodeGet everything needed to configure one node: its config fields (key, type, whether it's required, an example value, what it means), the output fields later steps can reference as {{ $json.field }}, whether it needs a credential and whether the user already has one, its output handles, and whether i…Get everything needed to configure one node: its config fields (key, type, whether it's required, an example value, what it means), the output fields later steps can reference as {{ $json.field }}, whether it needs a credential and whether the user already has one, its output handles, and whether i…
No se publicó ningún esquema de entrada para esta herramienta.
list_node_actionsList the operations an app node can perform — e.g. slack → send_message, list_channels — with what each one does, the OAuth scopes it needs, and which is the default. Also lists the resource pickers the node offers (channels, sheets, bases…) that resolve live from the user's credential.List the operations an app node can perform — e.g. slack → send_message, list_channels — with what each one does, the OAuth scopes it needs, and which is the default. Also lists the resource pickers the node offers (channels, sheets, bases…) that resolve live from the user's credential.
No se publicó ningún esquema de entrada para esta herramienta.
list_credentialsList the user's saved credentials by name, type and id. Secrets are never returned.List the user's saved credentials by name, type and id. Secrets are never returned.
No se publicó ningún esquema de entrada para esta herramienta.
create_credentialSave a new credential so nodes can authenticate. Use this for API-key / token style credentials — pass a name and the secret value.Save a new credential so nodes can authenticate. Use this for API-key / token style credentials — pass a name and the secret value.
No se publicó ningún esquema de entrada para esta herramienta.
create_automationBuild a brand-new automation from a plain-English description using Blinkbox's AI builder. Example: 'When a Stripe payment succeeds, send me a Slack DM'. Optionally activate it immediately.Build a brand-new automation from a plain-English description using Blinkbox's AI builder. Example: 'When a Stripe payment succeeds, send me a Slack DM'. Optionally activate it immediately.
No se publicó ningún esquema de entrada para esta herramienta.
blinkbox_api_getRead ANY Blinkbox REST endpoint the user owns (GET only). Use this for every read the named tools above don't already cover — analytics, profile, workspace members, versions, credential metadata, workflow and run details.Read ANY Blinkbox REST endpoint the user owns (GET only). Use this for every read the named tools above don't already cover — analytics, profile, workspace members, versions, credential metadata, workflow and run details.
No se publicó ningún esquema de entrada para esta herramienta.
blinkbox_apiFull control of Blinkbox: call ANY Blinkbox REST endpoint the user owns, with any HTTP method. For plain reads prefer blinkbox_api_get, which needs no approval. Use this for anything the named tools above don't already do — analytics, profile, workspace members/invites, credentials, versions, feedb…Full control of Blinkbox: call ANY Blinkbox REST endpoint the user owns, with any HTTP method. For plain reads prefer blinkbox_api_get, which needs no approval. Use this for anything the named tools above don't already do — analytics, profile, workspace members/invites, credentials, versions, feedb…
No se publicó ningún esquema de entrada para esta herramienta.
21 de 22 herramientas publicaron una descripción.
Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
Los nombres enlazados abren el índice de Forge con todas las entradas que se observó que exponen esa herramienta. Ver todas las herramientas indexadas.
Esta entrada no publica ningún paquete de npm, así que Forge no tiene un árbol de dependencias para ella. Es una carencia de cobertura, no una afirmación de que no tenga dependencias.