Testing utilities for CipherTrust Manager MCP Server
Testing utilities for CipherTrust Manager MCP Server. Exposed over MCP by the ciphertrust manager mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This project implements an independently-developed CipherTrust MCP (Model Context Protocol) server that allows AI Assistants like Claude or Cursor to interact with CipherTrust Manager resources using the ksctl CLI.
Everything the assistant can do here goes through one of these:
Dependencies — The pyproject.toml file includes these dependencies: - mcp>=1.0.0 - pydantic>=2.0.0 - pydantic-settings>=2.0.0 - httpx>=0.27.0 - python-dotenv>=1.0.0Support — This is an independent project. For official CipherTrust Manager support, please contact Thales directly. For issues with this unofficial MCP serverYou will need 5 environment variables: CIPHERTRUST_URL, CIPHERTRUST_USER, CIPHERTRUST_PASSWORD, KSCTL_PATH, KSCTL_CONFIG_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ciphertrust Manager's toolset — Dependencies, Support — is a fair guide to whether it matches your workflow. It is maintained by sanyambassi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ciphertrust Manager's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Dependencies | The pyproject.toml file includes these dependencies: - mcp>=1.0.0 - pydantic>=2.0.0 - pydantic-settings>=2.0.0 - httpx>=0.27.0 - python-dotenv>=1.0.0 |
| Support | This is an independent project. For official CipherTrust Manager support, please contact Thales directly. For issues with this unofficial MCP server, please use the GitHub issue tracker. |
**Windows Example:**
```json
{
"mcpServers": {
"ciphertrust": {
"command": "C:\\absolute\\path\\to\\ciphertrust-manager-mcp-server\\.venv\\Scripts\\ciphertrust-mcp-server",
"env": {
"CIPHERTRUST_URL": "https://your-ciphertrust.example.com",
"CIPHERTRUST_USER": "admin",
"CIPHERTRUST_PASSWORD": "your-password-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CIPHERTRUST_URL | Endpoint or connection string the server talks to. | Yes |
| CIPHERTRUST_USER | Configuration value read at startup. | Optional |
| CIPHERTRUST_PASSWORD | Configuration value read at startup. | Optional |
| KSCTL_PATH | Filesystem location the server is allowed to use. | Optional |
| KSCTL_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.