Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

List n8n Projects

n8n_list_projects
Read-onlyIdempotent

Retrieve all n8n projects to organize workflows and credentials into separate workspaces. Supports pagination and result limits for efficient workspace management.

Instructions

List all projects.

Projects help organize workflows and credentials into separate workspaces.

Args:

  • limit (number): Maximum results (default: 100)

  • cursor (string, optional): Pagination cursor

Returns: List of projects with id, name, and type (personal/team).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return
cursorNoPagination cursor

Implementation Reference

  • The handler function for the n8n_list_projects tool that fetches projects from the n8n API.
    async (params: z.infer<typeof ListProjectsSchema>) => {
      const queryParams: Record<string, unknown> = { limit: params.limit };
      if (params.cursor) queryParams.cursor = params.cursor;
      
      const response = await get<N8nPaginatedResponse<N8nProject>>('/projects', queryParams);
      
      const formatted = response.data.map(formatProject).join('\n\n');
      const output = {
        count: response.data.length,
        projects: response.data,
        nextCursor: response.nextCursor
      };
      
      let text = `Found ${response.data.length} project(s):\n\n${formatted}`;
      if (response.nextCursor) {
        text += `\n\n_More results available. Use cursor: ${response.nextCursor}_`;
      }
      
      return {
        content: [{ type: 'text', text }],
        structuredContent: output
      };
    }
  • Registration of the n8n_list_projects tool.
      server.registerTool(
        'n8n_list_projects',
        {
          title: 'List n8n Projects',
          description: `List all projects.
    
    Projects help organize workflows and credentials into separate workspaces.
    
    Args:
      - limit (number): Maximum results (default: 100)
      - cursor (string, optional): Pagination cursor
    
    Returns:
      List of projects with id, name, and type (personal/team).`,
          inputSchema: ListProjectsSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering safety and idempotency. The description adds value by mentioning pagination via the 'cursor' parameter and the return format ('List of projects with id, name, and type'), but doesn't detail rate limits, auth needs, or error handling. No contradiction with annotations.

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 well-structured with a purpose statement, context, and separate 'Args' and 'Returns' sections. It's front-loaded with the core action. However, the context sentence about projects could be slightly more integrated, and the repetition of schema info in 'Args' adds minor 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?

Given the tool's simplicity (list operation with 2 parameters), rich annotations (covering safety and idempotency), and 100% schema coverage, the description is mostly complete. It includes return value details despite no output schema. Minor gaps include lack of explicit sibling differentiation and deeper behavioral context like error cases.

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?

Schema description coverage is 100%, with clear descriptions for 'limit' and 'cursor' in the input schema. The description repeats this information in the 'Args' section, adding minimal value beyond the schema. The default for 'limit' is mentioned in both, but the description doesn't explain pagination behavior further. 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 verb ('List') and resource ('all projects'), and the title reinforces this. It distinguishes from sibling tools like 'n8n_get_project' (singular) and 'n8n_create_project' (creation). However, it doesn't explicitly differentiate from other list tools (e.g., 'n8n_list_workflows'), though the resource specificity is clear.

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 provides context about what projects are ('organize workflows and credentials into separate workspaces'), which implies usage for workspace management. It doesn't explicitly state when to use this tool versus alternatives like 'n8n_get_project' or other list tools, nor does it mention prerequisites or exclusions.

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