Skip to main content
Glama
modelcontextprotocol

Filesystem MCP Server

Official

Create Directory

create_directory
Idempotent

Create new directories or ensure existing ones are present, including nested structures, to set up project paths and required filesystem locations.

Instructions

Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • The handler function that executes the create_directory tool logic. It validates the provided path, creates the directory recursively using fs.mkdir, and returns a success message.
    async (args: z.infer<typeof CreateDirectoryArgsSchema>) => {
      const validPath = await validatePath(args.path);
      await fs.mkdir(validPath, { recursive: true });
      const text = `Successfully created directory ${args.path}`;
      return {
        content: [{ type: "text" as const, text }],
        structuredContent: { content: text }
      };
    }
  • Zod schema defining the input arguments for the create_directory tool: a single 'path' string parameter.
    const CreateDirectoryArgsSchema = z.object({
      path: z.string(),
    });
  • Registration of the create_directory tool with the MCP server, specifying title, description, input schema, output schema, annotations, and the handler function.
    server.registerTool(
      "create_directory",
      {
        title: "Create Directory",
        description:
          "Create a new directory or ensure a directory exists. Can create multiple " +
          "nested directories in one operation. If the directory already exists, " +
          "this operation will succeed silently. Perfect for setting up directory " +
          "structures for projects or ensuring required paths exist. Only works within allowed directories.",
        inputSchema: {
          path: z.string()
        },
        outputSchema: { content: z.string() },
        annotations: { readOnlyHint: false, idempotentHint: true, destructiveHint: false }
      },
      async (args: z.infer<typeof CreateDirectoryArgsSchema>) => {
        const validPath = await validatePath(args.path);
        await fs.mkdir(validPath, { recursive: true });
        const text = `Successfully created directory ${args.path}`;
        return {
          content: [{ type: "text" as const, text }],
          structuredContent: { content: text }
        };
      }
    );
Behavior4/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds valuable context beyond this: it specifies that the operation succeeds silently if the directory exists (elaborating on idempotency), mentions creating nested directories, and notes the constraint of allowed directories, which are not covered by annotations.

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 core functionality and efficiently structured in three sentences, each adding value: the first states the main action, the second elaborates on behavior, and the third provides usage context and constraints, with no wasted words.

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 moderate complexity (creation with idempotency and constraints), annotations cover safety aspects, and an output schema exists (so return values need not be explained). The description adds useful behavioral details like silent success and nested creation, but could benefit from more on error conditions or path examples for full 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?

Schema description coverage is 0%, so the description must compensate. It implies the 'path' parameter is used for creating directories and supports nested structures, but does not detail the path format, syntax, or examples. This adds some meaning beyond the bare schema but leaves gaps in parameter understanding.

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 the tool's purpose with specific verbs ('create', 'ensure exists') and resource ('directory'), distinguishing it from siblings like list_directory or move_file by focusing on creation/verification rather than listing or moving. It explicitly mentions creating nested directories, which further differentiates its functionality.

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 on when to use this tool ('Perfect for setting up directory structures for projects or ensuring required paths exist') and mentions a constraint ('Only works within allowed directories'), but it does not explicitly state when not to use it or name specific alternatives among siblings like directory_tree for viewing structures.

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/modelcontextprotocol/filesystem'

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