cellc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CELLC_BIN | No | Path to the cellc binary (if not found on PATH) | |
| CELLC_TIMEOUT | No | Per-call timeout in seconds (default 30) | 30 |
| CELLSCRIPT_REPO | No | Path to CellScript checkout for examples/reference (default ~/CellScript) | ~/CellScript |
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 |
|---|---|
| cellc_checkA | Type-check a CellScript contract. Returns ok + diagnostics (terse, max 5; full=true for all). |
| cellc_explainA | Explain a CellScript error code (e.g. E0014) with description and fix hint. |
| cellc_metadataC | Compiler-emitted metadata: resources, actions, effects, obligations. Summary by default. |
| cellc_constraintsC | Verifier obligations + runtime-error registry for a contract. Summary by default. |
| cellc_language_referenceA | The full CellScript language surface (keywords, effects, worked example). |
| cellc_list_examplesA | List bundled example .cell contracts with one-line summaries. |
| cellc_get_exampleB | Return one example .cell contract's source for few-shot grounding. |
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: type-checking (cellc_check), verifier obligations (cellc_constraints), error explanation (cellc_explain), examples (cellc_get_example, cellc_list_examples), language reference (cellc_language_reference), and metadata (cellc_metadata). No overlap in functionality.
All tools start with 'cellc_' prefix, but the naming pattern is inconsistent: some use verbs (cellc_check, cellc_explain, cellc_get_example, cellc_list_examples) while others are nouns (cellc_constraints, cellc_language_reference, cellc_metadata). This mixed convention reduces predictability.
With 7 tools covering essential aspects of CellScript contract development (checking, constraints, error help, examples, language reference, metadata), the count is well-scoped and appropriate for the domain.
The tool set covers key workflows: type-checking, error resolution, language reference, and example retrieval. Minor gaps exist (e.g., no tool to fetch a specific example by name or compile a contract), but the core development cycle is supported.