Skip to main content
Glama

create-project

Initiate new projects in n8n by specifying client ID and project name via compact JSON input. Requires n8n Enterprise with project management enabled.

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

  • Handler logic for the 'create-project' tool. Retrieves the N8nClient instance using clientId, validates it exists, then calls the client's createProject method with the provided name, handling success and error responses.
    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
        };
      }
    }
  • Input schema definition for the 'create-project' tool, specifying clientId and name as required string parameters.
    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"]
    }
  • src/index.ts:519-528 (registration)
    Registration of the 'create-project' tool in the ListToolsRequestSchema handler's tools array.
    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"]
    }
  • N8nClient helper method that makes a POST request to '/projects' with the project name to create a new project.
    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 behavioral traits such as the license requirement and input format constraint ('Arguments must be provided as compact, single-line JSON'). However, it doesn't cover other aspects like error handling, response format, or mutation effects beyond creation. This adds some value but is incomplete 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.

Conciseness5/5

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

The description is front-loaded with the core purpose, followed by important notes in two concise sentences. Every sentence adds value: the first states the action, the second specifies prerequisites, and the third details input requirements. No wasted words.

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 no annotations and no output schema, the description provides some context like license needs and input format, but lacks details on return values, error cases, or full parameter meanings. For a creation tool with 2 parameters, this is minimally adequate but has clear gaps in completeness.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'Arguments must be provided as compact, single-line JSON' which adds context about parameter format, but doesn't explain the semantics of 'clientId' and 'name' parameters. This partial compensation is insufficient given the low 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 verb 'Create' and the resource 'new project in n8n', making the purpose evident. However, it doesn't explicitly differentiate this from sibling tools like 'update-project' or 'delete-project', though the action is distinct by name. The description is specific but lacks sibling comparison.

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 explicit context for when to use this tool by stating 'Requires n8n Enterprise license with project management features enabled', which acts as a prerequisite. It doesn't mention alternatives like 'update-project' or exclusions, but the license requirement gives clear usage conditions.

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

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

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