Skip to main content
Glama
Infisical

Infisical MCP Server

Official
by Infisical

create-folder

Create and organize folders in Infisical for structured secret management. Specify folder name, project ID, environment, optional path, and description for efficient organization.

Instructions

Create a new folder in Infisical

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoThe description of the folder to create
environmentYesThe environment to create the folder in (required)
nameYesThe name of the folder to create (required)
pathNoThe path to create the folder in (Defaults to /)
projectIdYesThe project to create the folder in (required)

Implementation Reference

  • Handler for the 'create-folder' tool: validates input using Zod schema, creates the folder via Infisical SDK, and returns the result as text content.
    if (name === AvailableTools.CreateFolder) {
    	const data = createFolderSchema.zod.parse(args);
    
    	const folder = await infisicalSdk.folders().create({
    		description: data.description,
    		environment: data.environment,
    		name: data.name,
    		path: data.path,
    		projectId: data.projectId
    	});
    
    	return {
    		content: [
    			{
    				type: "text",
    				text: `Folder created successfully: ${JSON.stringify(folder, null, 3)}`
    			}
    		]
    	};
    }
  • Input schema (Zod and JSON Schema capability) defining parameters for the 'create-folder' tool: projectId, environment, name, path, description.
    const createFolderSchema = {
    	zod: z.object({
    		description: z.string().optional(),
    		environment: z.string(),
    		name: z.string(),
    		path: z.string().default("/"),
    		projectId: z.string()
    	}),
    	capability: {
    		name: AvailableTools.CreateFolder,
    		description: "Create a new folder in Infisical",
    		inputSchema: {
    			type: "object",
    			properties: {
    				description: {
    					type: "string",
    					description: "The description of the folder to create"
    				},
    				environment: {
    					type: "string",
    					description: "The environment to create the folder in (required)"
    				},
    				name: {
    					type: "string",
    					description: "The name of the folder to create (required)"
    				},
    				path: {
    					type: "string",
    					description: "The path to create the folder in (Defaults to /)"
    				},
    				projectId: {
    					type: "string",
    					description: "The project to create the folder in (required)"
    				}
    			},
    			required: ["name", "projectId", "environment"]
    		}
    	}
    };
  • src/index.ts:452-467 (registration)
    Tool registration in ListToolsRequestSchema handler by including createFolderSchema.capability in the list of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
    	return {
    		tools: [
    			createSecretSchema.capability,
    			deleteSecretSchema.capability,
    			updateSecretSchema.capability,
    			listSecretsSchema.capability,
    			getSecretSchema.capability,
    			createProjectSchema.capability,
    			createEnvironmentSchema.capability,
    			createFolderSchema.capability,
    			inviteMembersToProjectSchema.capability,
    			listProjectsSchema.capability
    		]
    	};
    });
  • Enum defining all tool names as constants, including CreateFolder = "create-folder", used for matching tool names in handlers and schemas.
    enum AvailableTools {
    	CreateSecret = "create-secret",
    	DeleteSecret = "delete-secret",
    	UpdateSecret = "update-secret",
    	ListSecrets = "list-secrets",
    	GetSecret = "get-secret",
    	CreateProject = "create-project",
    	CreateEnvironment = "create-environment",
    	CreateFolder = "create-folder",
    	InviteMembersToProject = "invite-members-to-project",
    	ListProjects = "list-projects"
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a folder but doesn't mention permissions required, whether the operation is idempotent, error conditions, or what happens on success (e.g., returns a folder ID). This is a significant gap 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error handling, or return values, leaving critical gaps for an AI agent to understand how to use it effectively.

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%, so the input schema fully documents all 5 parameters with their types and requirements. The description adds no parameter-specific information beyond what's in the schema, but this is acceptable given the high coverage, resulting in a baseline 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 action ('Create a new folder') and the target system ('in Infisical'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'create-project' or 'create-environment' beyond the resource type, missing explicit 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 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 'create-project' or 'create-environment', nor does it mention prerequisites or exclusions. It lacks any context for tool selection among the available creation tools.

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/Infisical/infisical-mcp-server'

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