Skip to main content
Glama

create-project

Create new projects in n8n workflow automation platform. This tool enables users to set up and organize automation projects within n8n Enterprise environments.

Instructions

Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes
nameYes

Implementation Reference

  • Main execution handler for the 'create-project' tool. Retrieves the N8nClient by clientId, validates it exists, calls client.createProject(name), and returns success or error response.
    case "create-project": {
      const { clientId, name } = args as { clientId: string; name: string };
      const client = clients.get(clientId);
      if (!client) {
        return {
          content: [{
            type: "text",
            text: "Client not initialized. Please run init-n8n first.",
          }],
          isError: true
        };
      }
    
      try {
        await client.createProject(name);
        return {
          content: [{
            type: "text",
            text: `Successfully created project: ${name}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • src/index.ts:519-528 (registration)
    Tool registration entry in the ListToolsRequestHandler response, defining the name, description, and input schema for 'create-project'.
    name: "create-project",
    description: "Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
    inputSchema: {
      type: "object",
      properties: {
        clientId: { type: "string" },
        name: { type: "string" }
      },
      required: ["clientId", "name"]
    }
  • Input schema definition for the 'create-project' tool, specifying required parameters: clientId (string) and name (string).
    name: "create-project",
    description: "Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
    inputSchema: {
      type: "object",
      properties: {
        clientId: { type: "string" },
        name: { type: "string" }
      },
      required: ["clientId", "name"]
    }
  • Helper method in N8nClient class that performs the actual API call to create a project by POSTing to /projects with the project name.
    async createProject(name: string): Promise<void> {
      return this.makeRequest<void>('/projects', {
        method: 'POST',
        body: JSON.stringify({ name }),
      });
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: the licensing requirement and the JSON formatting constraint ('Arguments must be provided as compact, single-line JSON'). However, it doesn't cover other aspects like error handling, response format, or side effects, leaving gaps for a mutation tool.

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 appropriately sized with two sentences: one for the core purpose and prerequisites, and another for technical constraints. It's front-loaded with the main action. While efficient, the second sentence could be more integrated, but overall it earns its place without waste.

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?

Given the complexity (a creation tool with licensing requirements), no annotations, no output schema, and poor parameter documentation, the description is incomplete. It covers licensing and formatting but misses parameter details, expected outputs, and error scenarios. It's minimally adequate but with clear gaps for effective use.

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

Parameters2/5

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

The input schema has 0% description coverage, with two required parameters (clientId and name) undocumented. The description adds no meaning about what these parameters represent, their formats, or examples. It only mentions JSON formatting generally, failing to compensate for the schema gap, resulting in a low score.

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 verb 'Create' and the resource 'new project in n8n', making the purpose explicit. It distinguishes from siblings like 'update-project' or 'delete-project' by specifying creation. However, it doesn't explicitly differentiate from 'create-workflow' or 'create-credential' beyond the resource type, keeping it at 4 rather than 5.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'Requires n8n Enterprise license with project management features enabled' establishes prerequisites. It implies usage for project creation versus alternatives like 'update-project' or 'list-projects', but doesn't explicitly state when-not-to-use or name specific alternatives, so it scores 4.

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/illuminaresolutions/n8n-mcp-server'

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