Equinox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EQUINOX_DOCS_PATH | No | Path to local Equinox docs directory (offline mode) | |
| EQUINOX_MCP_NO_CACHE | No | Set to 1 to disable caching | 0 |
| EQUINOX_MCP_CACHE_DIR | No | Cache directory for online mode | ~/.cache/equinox-mcp |
| EQUINOX_MCP_CACHE_TTL | No | Cache TTL in hours | 24 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-sectionsA | List all available Equinox documentation sections. Returns section titles, paths, and use cases to help identify relevant docs. |
| get-documentationB | Retrieve full documentation for requested sections. Accepts section name(s) or path(s) like 'attention', 'api/nn/attention', or ['module', 'pattern']. |
| equinox-checkerC | Analyze Equinox module code and suggest fixes. Checks PyTree compliance, init signature, call signature, and common mistakes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| equinox-task | Guide for working with Equinox - patterns, tools, and best practices |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: equinox-checker analyzes code, get-documentation retrieves specific documentation, and list-sections lists available documentation sections. There is no overlap in functionality, making it easy for an agent to select the correct tool.
The tools follow a consistent verb-noun pattern with hyphens (e.g., equinox-checker, get-documentation, list-sections), which is readable and predictable. The minor deviation is that equinox-checker includes a prefix, but overall naming is coherent.
With 3 tools, the server is well-scoped for its purpose of analyzing Equinox code and accessing documentation. This count is reasonable, though slightly on the lower side, as it covers core workflows without being overwhelming.
The tools provide good coverage for code analysis and documentation retrieval in the Equinox domain. Minor gaps might exist, such as no direct tool for generating code or handling advanced debugging, but the set supports common agent tasks effectively.