Skip to main content
Glama
Sign In
Infisical MCP Server

Infisical MCP Server

Official
by Infisical
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create-environment

Create a new environment in an Infisical project using project ID, name, and slug. Optionally set a position to control ordering.

Instructions

Create a new environment 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": {
      "projectId": "<projectId>",
      "name": "<name>",
      "slug": "<slug>"
    },
    "name": "create-environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the environment to create (required)
slugYesThe slug of the environment to create (required)
positionNoThe position of the environment to create
projectIdYesThe ID of the project to create the environment in (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already convey mutation (readOnlyHint=false) and non-idempotence; the description's 'Create' adds no further behavioral context such as side effects, duplicate handling, permission requirements, or response behavior. With annotations present the bar is lower, but the description still contributes essentially no beyond-annotation behavior.

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 a single short sentence with no filler, and the core action and target are front-loaded. However, it is so terse that it provides little information beyond the tool name, so while efficient, it is not exemplary content.

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?

For a create operation with four simple parameters and full schema coverage, the combination is just sufficient to construct a valid call. It is not fully complete because there is no output schema, no indication of what the successful response contains, and the relationship to project creation is left implicit.

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% and each parameter has its own description, so the schema fully carries the semantic burden. The tool description adds nothing about parameters, so the baseline score of 3 is appropriate.

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 names a specific action ('Create') on a specific resource ('environment') and the system ('Infisical'), which is enough to distinguish it from sibling tools like create-project, create-secret, and create-folder at a glance. It does not explain what an environment is or how it relates to those other resources, so it stops short of full clarity.

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 on when to use this tool, whether an existing project is a prerequisite, or how it compares to alternatives like create-project or create-folder. The agent must infer context solely from the required projectId parameter.

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