Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
blinkboxNo description publishedThis tool published no description. Forge does not invent one.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
rename_automationprivilegedRename an automation (look it up by current name or id).Rename an automation (look it up by current name or id).
No input schema was published for this tool.
delete_automationprivilegedPermanently delete an automation by name or id. This cannot be undone.Permanently delete an automation by name or id. This cannot be undone.
No input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
21 of 22 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.