n8n MCP Server

Overview Schema Source Related Servers Discussions Admin

Create n8n Project

n8n_create_project

Create a new n8n project to organize workflows and credentials. Group related automation assets in one place for easier management.

Instructions

Create a new project for organizing workflows and credentials.

Args:

name (string): Project name

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": {
      "name": "<name>"
    },
    "name": "n8n_create_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Project name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already indicate this is a mutation (readOnlyHint false), non-idempotent, and non-destructive. The description adds only the purpose clause, offering no extra behavioral context such as name uniqueness, permissions, or side effects. It does not contradict annotations but contributes little beyond what structured data already conveys.

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

Conciseness4/5

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

The description is short and front-loaded with the main action. The 'Args' block duplicates schema information, adding minor redundancy, but overall it remains concise and well-structured.

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

Completeness2/5

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

With no output schema, the description should clarify return values or creation effects; it does not. It explains what a project is for but omits any prerequisite or post-creation behavior. For a simple tool, this is a notable gap that leaves the agent uncertain about what happens after the call.

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

Parameters3/5

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

The schema fully documents the single 'name' parameter with type, minLength, and description. The description repeats this as 'Args: name (string): Project name', adding no new semantic detail. Baseline 3 is appropriate since the schema carries the full burden.

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 clearly states 'Create a new project for organizing workflows and credentials.' It identifies the specific verb (create) and resource (project), and differentiates from sibling create tools (workflow, credential, tag, variable) by naming the resource type and its purpose.

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 one needs a project to organize workflows and credentials, but it provides no explicit when-to-use guidance or alternatives. No exclusions or prerequisites are mentioned, so the agent gets minimal direction on selecting this tool over other n8n create tools.

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

Deploy Server