Infisical MCP Server
OfficialRelated Servers
Alternatives to Infisical MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with direct access to secrets management (get, set, list, delete secrets, and list environments) through the Model Context Protocol, enabling secure secret operations during development.13 npmMIT
- FlicenseNot gradedqualityDmaintenanceFastMCP server for managing a self-hosted Infisical instance, exposing tools to create, read, update, and delete projects, environments, folders, and secrets, and to render .env and shell-export formats.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.321 PyPI6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.1MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API for streamlined project management workflows.640MIT
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: secret CRUD (create, get, list, update, delete) is clearly separated from project/environment/folder creation and member invitations. No two tools have overlapping or ambiguous purposes.
All tool names follow a consistent kebab-case verb-noun pattern (e.g., create-secret, list-secrets, update-secret). The singular vs. plural use is logical (list for multiple, others for single) and makes the naming predictable across the set.
10 tools is within the ideal 3-15 range for a focused server. Each tool serves a clear purpose in secrets management or project scaffolding, with no unnecessary redundancy or bloat.
Secrets are fully covered with CRUD, but the server lacks essential operations for the other entities it creates: there is no get/update/delete for projects, environments, or folders, and no list-environment/list-folder tools. This leaves obvious gaps where agents cannot manage or retrieve the resources they create.