CompText MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CTXT_BIN | No | Path to the ctxt executable. Optional if ctxt is in PATH. | |
| CTXT_WORKDIR | Yes | Path to the Rust project workspace. | |
| CTXT_TIMEOUT_SECS | No | Timeout in seconds for operations (default may be 30). | |
| CTXT_MCP_READ_ONLY | No | Set to '1' for read-only mode (default). Set to '0' to disable read-only. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| comptext_statusB | Return CompText, Rust, Cargo, Git, and workspace status. |
| comptext_pack_contextC | Create a deterministic context pack with stable file order and sha256 hashes. |
| comptext_rust_auditC | Run safe read-only Rust checks. |
| comptext_replay_digestC | Create a deterministic replay/evidence digest for the current workspace. |
| comptext_contract_checkC | Check local safety contracts for OpenCode usage. |
| comptext_github_packA | Prepare a local GitHub summary pack without network calls. |
| comptext_hf_export_packA | Return Hugging Face Space/Card export text without upload or token usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: contract checking, GitHub packaging, Hugging Face export, context packing, replay digest, Rust audit, and status. There is no overlap or ambiguity.
All tools follow a consistent 'comptext_' prefix followed by descriptive snake_case names (e.g., comptext_contract_check, comptext_status). The pattern is uniform and predictable.
With 7 tools, the count is well within the ideal range (3-15). Each tool serves a clear function without excess or deficiency for the server's apparent scope.
The tools cover core workflows: contract checks, exports, context packing, digests, audits, and status. Minor gaps might exist (e.g., no tool for clearing or resetting state), but the set is largely complete for typical usage.