Thales Ciphertrust Manager Mcp Server

What is Thales Ciphertrust Manager Mcp Server?

An independently-developed, open-source MCP server that enables AI assistants (like Claude and Cursor) to interact with CipherTrust Manager resources using the ksctl CLI. It is not officially supported by Thales, uses public APIs, and is maintained independently.

How to use Thales Ciphertrust Manager Mcp Server?

Install Git, Python 3.11+, and uv. Clone the repository, create a virtual environment, and install dependencies with uv pip install -e .. Configure required environment variables (CIPHERTRUST_URL, CIPHERTRUST_USER, CIPHERTRUST_PASSWORD) either in a .env file or system environment. Run the server directly with uv run ciphertrust-mcp-server or as a module uv run python -m ciphertrust_mcp_server.__main__. For integration with Cursor or Claude Desktop, set up the MCP configuration file with the correct command path and environment variables.

Features of Thales Ciphertrust Manager Mcp Server

• Key management operations (list, create, delete, etc.)
• CTE client management
• User and group management
• Connection management
• System, service, cluster, license management
• JSON-RPC communication over stdin/stdout

Use cases of Thales Ciphertrust Manager Mcp Server

• Automate key lifecycle tasks via AI assistant prompts
• Manage CTE clients and user permissions through natural language
• Retrieve system information and cluster status without manual CLI
• Perform crypto operations and license management with AI guidance

FAQ from Thales Ciphertrust Manager Mcp Server

Is this server officially supported by Thales?

No, this is an independent open-source project with no official support from Thales. Use at your own risk.

What are the runtime dependencies?

Python 3.11+ and the packages mcp, pydantic, pydantic-settings, httpx, and python-dotenv.

How does the server communicate with AI assistants?

It uses JSON-RPC protocol over stdin/stdout, configured via MCP settings in Cursor or Claude Desktop.

Where is sensitive data (credentials) stored?

Credentials are provided as environment variables (CIPHERTRUST_USER, CIPHERTRUST_PASSWORD) or in a .env file. SSL verification can be disabled with CIPHERTRUST_NOSSLVERIFY.

What transport and authentication methods are supported?

Transport is stdin/stdout (standard I/O). Authentication uses username/password to the CipherTrust Manager instance, with optional domain settings (CIPHERTRUST_DOMAIN, CIPHERTRUST_AUTH_DOMAIN).