Skip to main content
Glama
Sign In
Infisical MCP Server

Infisical MCP Server

Official
by Infisical
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create-project

Create a new project in Infisical by specifying its name and type, with optional slug, description, KMS key, and template.

Instructions

Create a new project in Infisical

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectName": "<projectName>",
      "type": "<type>"
    },
    "name": "create-project"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
kmsKeyIdNoThe ID of the KMS key to use for the project. Defaults to Infisical's default KMS
descriptionNoThe description of the project to create
projectNameYesThe name of the project to create (required)
projectTemplateNoThe template of the project to create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.24
    • addedInput schema / properties / type / enum
      Added value: +[
+  "secret-manager",
+  "cert-manager",
+  "kms",
+  "secret-scanning",
+  "pam"
+]
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint false), non-idempotent, and non-destructive. The description adds no additional behavioral details such as permissions required, reversibility, or potential side effects. It does not contradict annotations but also does not enrich them.

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, concise sentence that front-loads the action. It contains no unnecessary words and is efficiently structured.

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?

The tool is straightforward, and the schema covers parameters. However, the description omits any mention of return values, potential errors, or additional context like whether the project name must be unique. Given the absence of an output schema and the tool's moderate complexity, a slightly richer description would be more complete, but it is minimally adequate.

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 covers 100% of parameters with descriptions, so the description is not responsible for parameter meaning. The description adds no extra parameter semantics beyond what the schema already provides, which meets the baseline for full coverage.

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 action ('Create') and the resource ('a new project') within the system ('Infisical'). It is specific and distinguishes from sibling tools like create-secret or create-environment, which target different resource types.

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 or any exclusions. While the tool name and sibling context make the purpose obvious, the description itself offers no usage context, such as prerequisites or conditions for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools