HestAI-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HESTAI_PROJECT_ROOT | No | Optional override to control the location of .hestai-sys. If not set, defaults to the current working directory. | |
| HESTAI_GOVERNANCE_ENABLED | No | Set to 'true' to force governance injection even if no .hestai/ directory exists. Default behavior: governance only runs if .hestai/ directory exists. |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| octave_validateA | Schema check + repair suggestions for OCTAVE content. Validates content against schema, returns canonical form with optional repairs. Focus on I3 (Mirror Constraint) and I5 (Schema Sovereignty). |
| octave_writeA | Unified entry point for writing OCTAVE files. Handles creation (new files) and modification (existing files). Use content for full payload, changes for delta updates. Omit both content and changes to normalize an existing file in-place. Replaces octave_create and octave_amend. |
| octave_ejectA | Eject OCTAVE content with projection modes. Supports canonical, authoring, executive, and developer views. Can generate templates when content is null. Output formats: octave, json, yaml, markdown, gbnf. |
| octave_compile_grammarA | Compile OCTAVE schema or contract to constraint grammar. Supports GBNF (llama.cpp) and JSON Schema (vLLM) output formats. Provide either a builtin schema name or inline OCTAVE content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| grammar/AGENT_DEFINITION | Pre-compiled GBNF grammar for the AGENT_DEFINITION schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/COGNITION_DEFINITION | Pre-compiled GBNF grammar for the COGNITION_DEFINITION schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/CRS_REVIEW | Pre-compiled GBNF grammar for the CRS_REVIEW schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/DEBATE_TRANSCRIPT | Pre-compiled GBNF grammar for the DEBATE_TRANSCRIPT schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/DECISION_LOG | Pre-compiled GBNF grammar for the DECISION_LOG schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/META_SCHEMA | Pre-compiled GBNF grammar for the META_SCHEMA schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/SKILL | Pre-compiled GBNF grammar for the SKILL schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/TEST_HOLOGRAPHIC | Pre-compiled GBNF grammar for the TEST_HOLOGRAPHIC schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
TDQS
Scored across 4 tools
Each tool has a distinct, non-overlapping purpose: grammar compilation, content ejection, validation, and writing. No ambiguity.
All tools follow a consistent 'octave_verb' pattern with clear action nouns (compile_grammar, eject, validate, write).
4 tools is well-scoped for a domain-specific server covering compilation, validation, output, and file manipulation.
The tool set covers the core lifecycle of OCTAVE content: compile, validate, output (eject), and write (create/modify/normalize). No obvious gaps.