Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
N8N_URLNoThe address of your n8n instance. Together with N8N_API_KEY, enables uploads of converted workflows to n8n (create a new, inactive workflow).
N8N_API_KEYNoYour n8n API key (n8n → Settings → n8n API). Together with N8N_URL, enables uploads of converted workflows to n8n.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
convert_makeA

Convert one Make (Integromat) scenario blueprint (the .json from Export Blueprint) into an n8n workflow. Runs locally; nothing is sent anywhere. Writes .n8n.json (import it in n8n), plus the report as Markdown and JSON, to outputDir. Returns the report: totals (converted / to review / manual), every step with its n8n node and status, a concrete suggestion for each step to finish by hand, the credentials and webhook URLs to set up, and the paths of the files. For Zapier exports use convert_zapier instead. Afterwards, upload_to_n8n (when configured) creates the workflow in n8n, and check_n8n_workflow re-checks a file after manual edits.

convert_zapierA

Convert zaps from a Zapier export (Settings → Security and data → Download my Zap workflows; one JSON file holds all zaps) into n8n workflows. Runs locally; nothing is sent anywhere. Writes one .n8n.json plus a Markdown and JSON report per zap to outputDir, and returns the reports: totals, every step with its n8n node and status, suggestions for the steps to finish by hand, and the file paths. When the export holds many zaps, call list_zaps first and pass the chosen titles or ids in "zaps". For Make blueprints use convert_make instead.

list_zapsA

List the zaps in a Zapier export without converting anything: id, title, number of steps, apps used and on/off state of each. Use it before convert_zapier when the export holds more than a few zaps, so the user can choose which ones to convert. Reads the file only; writes nothing.

suggest_replacementA

Explain how one Make module or Zapier step is handled, without converting a file: whether it converts automatically and to which n8n node, or which n8n app node, HTTP request to the app's API, or Code node to use instead, with the steps to set it up. Use it when the user asks about a single module, or to explain a step a report marked review or manual.

supported_modulesA

List the Make modules and Zapier steps that convert automatically, as a table of module key and the n8n node it becomes. Use it to answer "does X convert?" before the user exports anything; for one known key, suggest_replacement gives more detail. Modules not listed still convert to a placed, disabled n8n node with a suggestion.

check_n8n_workflowA

Check an n8n workflow JSON file for problems that stop it from importing or running: broken connections, duplicate node names, disabled steps left, REPLACE-ME placeholders and credentials still to pick. Use it after the user finished steps by hand, or on any n8n workflow. Returns one line per problem (error, warning or info), or "No problems found". Reads the file only; writes nothing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation4/5

Conversion tools are cleanly split by source (Make vs Zapier) and explicitly cross-reference each other, and list_zaps/check_n8n_workflow have clearly distinct jobs. The only mild overlap is between supported_modules and suggest_replacement, which both answer 'does X convert?', though the descriptions do explain when to use which.

Naming Consistency4/5

Most tools follow a verb_noun pattern (convert_make, convert_zapier, list_zaps, suggest_replacement, check_n8n_workflow) with consistent snake_case. supported_modules is a noun-only outlier, a minor deviation from the otherwise predictable scheme.

Tool Count5/5

Six tools is well-scoped for a converter: two conversion entry points, one listing helper, two explanation/lookup tools, and one validator. Each earns its place with no filler.

Completeness3/5

The surface covers convert, inspect, explain, and validate, but convert_make's description points to an upload_to_n8n tool that is not in the set, creating a dead-end reference for pushing workflows into n8n. There is also no tool for editing or fixing an output file beyond re-checking it.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues