Skip to main content
Glama
Infisical

Infisical MCP Server

Official
by Infisical

create-project

Initialize a project in Infisical by specifying its name, type, and optional details like description, slug, and template to streamline secret management configuration.

Instructions

Create a new project in Infisical

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoThe description of the project to create
kmsKeyIdNoThe ID of the KMS key to use for the project. Defaults to Infisical's default KMS
projectNameYesThe name of the project to create (required)
projectTemplateNoThe template of the project to create
slugNoThe slug of the project to create
typeYesThe type of project to create (required). If not specified by the user, ask them to confirm the type they want to use.

Implementation Reference

  • Handler function for the 'create-project' tool. Parses input arguments using the schema, calls infisicalSdk.projects().create() with the provided parameters, and returns the created project details.
    if (name === AvailableTools.CreateProject) {
    	const data = createProjectSchema.zod.parse(args);
    
    	const project = await infisicalSdk.projects().create({
    		projectName: data.projectName,
    		projectDescription: data.description,
    		kmsKeyId: data.kmsKeyId,
    		slug: data.slug,
    		template: data.projectTemplate,
    		type: data.type
    	});
    
    	return {
    		content: [
    			{
    				type: "text",
    				text: `Project created successfully: ${JSON.stringify(project, null, 3)}`
    			}
    		]
    	};
    }
  • Zod schema for input validation and capability definition (name, description, inputSchema) for the 'create-project' tool.
    const createProjectSchema = {
    	zod: z.object({
    		projectName: z.string(),
    		type: z.enum(["secret-manager", "cert-manager", "kms", "ssh"]),
    		description: z.string().optional(),
    		slug: z.string().optional(),
    		projectTemplate: z.string().optional(),
    		kmsKeyId: z.string().optional()
    	}),
    	capability: {
    		name: AvailableTools.CreateProject,
    		description: "Create a new project in Infisical",
    		inputSchema: {
    			type: "object",
    			properties: {
    				projectName: {
    					type: "string",
    					description: "The name of the project to create (required)"
    				},
    				type: {
    					type: "string",
    					description:
    						"The type of project to create (required). If not specified by the user, ask them to confirm the type they want to use."
    				},
    				description: {
    					type: "string",
    					description: "The description of the project to create"
    				},
    				slug: {
    					type: "string",
    					description: "The slug of the project to create"
    				},
    				projectTemplate: {
    					type: "string",
    					description: "The template of the project to create"
    				},
    				kmsKeyId: {
    					type: "string",
    					description: "The ID of the KMS key to use for the project. Defaults to Infisical's default KMS"
    				}
    			},
    			required: ["projectName", "type"]
    		}
    	}
    };
  • src/index.ts:452-467 (registration)
    Registration of the 'create-project' tool in the list of available tools returned by ListToolsRequestSchema handler.
    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 the tool names, including 'create-project' used 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. While 'Create' implies a write operation, the description doesn't address permissions needed, whether the operation is idempotent, what happens on conflicts, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 states the core purpose without unnecessary elaboration. It's appropriately sized and front-loaded with the essential information.

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 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain behavioral aspects like permissions, idempotency, or response format, leaving significant gaps in understanding how to use the tool 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?

The schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema descriptions, maintaining the baseline score for 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 ('Create') and resource ('new project in Infisical'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'create-environment' or 'create-folder' beyond specifying the resource type.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, when not to use it, or how it relates to sibling tools like 'create-environment' or 'invite-members-to-project'.

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