Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Install n8n Community Package

n8n_install_community_package

Install a community node package from npm into your n8n instance. Specify the npm package name and optionally a version to extend n8n with custom nodes.

Instructions

Install a community node package from npm.

Args:

  • packageName (string): npm package name (e.g., 'n8n-nodes-evolution-api')

  • version (string?): Specific version to install (default: latest)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageName": "<packageName>"
    },
    "name": "n8n_install_community_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoSpecific version (default: latest)
packageNameYesnpm package name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate this is not read-only (readOnlyHint=false) and not idempotent. The description adds no extra behavioral context such as side effects, network requirements, or permissions. It simply restates the install action without discussing reversibility or impact on the n8n instance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: a clear one-line purpose and a compact args list. Every word earns its place, with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple install tool with two well-documented parameters and no output schema, the description is largely sufficient. It could mention that the installed package becomes visible via list_community_packages, but this is not essential for invoking the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by providing a concrete example ('n8n-nodes-evolution-api') and clarifying the version default ('latest'), which helps the agent format arguments correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Install' and identifies the resource as 'a community node package from npm', clearly distinguishing from sibling tools like list_community_packages and uninstall_community_package. The title reinforces the action, but the description adds the npm source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you need to install a community node package, but it does not explicitly state when to use this tool over alternatives or mention prerequisites (e.g., n8n instance access). The context is clear but lacks explicit exclusions or alternative references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools