n8n Advisor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | Yes | API key from n8n Settings > API | |
| N8N_BASE_URL | Yes | Base URL of your n8n instance (no trailing slash) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_workflowsA | Reviews all workflows and reports status. Shows total count, active/inactive breakdown, and identifies workflows with recent errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or ambiguity between tools.
With a single tool, naming is trivially consistent and follows a logical verb_noun pattern.
A single read-only 'check' tool is insufficient for an 'Advisor' server, which implies broader capabilities like querying, analyzing, or modifying workflows.
The tool surface is severely incomplete: it offers only one check operation with no ability to act on workflows, retrieve details, or perform any state changes.