Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Create n8n Project

n8n_create_project

Create a new project in n8n to organize workflows and credentials by providing a project name.

Instructions

Create a new project for organizing workflows and credentials.

Args:

  • name (string): Project name

Returns: The created project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name

Implementation Reference

  • The registration and handler implementation for the n8n_create_project tool.
      server.registerTool(
        'n8n_create_project',
        {
          title: 'Create n8n Project',
          description: `Create a new project for organizing workflows and credentials.
    
    Args:
      - name (string): Project name
    
    Returns:
      The created project.`,
          inputSchema: CreateProjectSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: false,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof CreateProjectSchema>) => {
          const project = await post<N8nProject>('/projects', params);
          
          return {
            content: [{ type: 'text', text: `✅ Project created!\n\n${formatProject(project)}` }],
            structuredContent: project
          };
        }
      );
Behavior3/5

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

Annotations indicate this is a non-readOnly, non-destructive, non-idempotent, non-openWorld operation, covering basic behavioral traits. The description adds that it creates a project 'for organizing workflows and credentials,' providing some context about the project's purpose, but doesn't elaborate on permissions, rate limits, or creation constraints beyond what annotations imply.

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 front-loaded with the core purpose in the first sentence, followed by structured Args and Returns sections. It's efficient with minimal waste, though the Args section could be omitted since it duplicates schema info without added value.

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

Completeness3/5

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

For a creation tool with annotations covering safety and no output schema, the description is minimally adequate. It states what is created and the single parameter, but lacks details on return values (only mentions 'The created project' vaguely) and doesn't address potential errors or project limits, leaving gaps in completeness.

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 input schema has 100% description coverage, with the 'name' parameter fully documented in the schema. The description repeats 'Project name' in the Args section but adds no additional semantic context (e.g., naming conventions, uniqueness requirements). Baseline 3 is appropriate given high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Create a new project') and the resource ('for organizing workflows and credentials'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'n8n_update_project' or 'n8n_list_projects', which would require a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'n8n_update_project' or 'n8n_list_projects', nor does it mention prerequisites or context for creating a project. It simply states what the tool does without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DrBalls/n8n-mcp-server-v2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server