liara-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Where chunks.jsonl, embeddings.npz and corpus_meta.json live. | packaged data/ |
| EMBED_DIM | No | Same. A different-width model is caught here; a same-width one is caught by the provenance hash. | 1536 |
| LOG_LEVEL | No | Logs go to stderr; stdout is the stdio wire. | INFO |
| EMBED_MODEL | No | Must match what embeddings.npz was built with, or the matrix is refused at load. | text-embedding-3-small |
| AVALAI_API_KEY | No | Turns on the dense retrieval list. The only outbound call this server makes. | |
| NO_PROXY_HOSTS | No | Hosts to keep away from a local proxy. api.avalai.ir answers in 0.2 s directly and hangs for 30 s through one. | api.avalai.ir |
| AVALAI_BASE_URL | No | Any OpenAI-compatible /embeddings endpoint. | https://api.avalai.ir/v1 |
| MCP_ALLOWED_HOSTS | No | --http only. See above. | |
| MCP_ALLOWED_ORIGINS | No | --http only. Browsers, and nothing else, send Origin. Requires MCP_ALLOWED_HOSTS. |
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 |
|---|---|
| search_docsA | Search the Liara documentation and return numbered snippets with their source URLs. Use this for every factual claim about Liara. Write the query in the user's own words plus the product name; Persian and English both work. Args: query: What to search for. Longer than 300 characters is truncated. k: How many snippets to return, 1 to 8. Values outside that range are clamped. |
| read_pageA | Read one whole documentation page from the local corpus. The URL must be one a previous search returned. No other URL can be fetched: this server has no HTTP client on the tool path and reads only what is already indexed. Args: url: A canonical docs.liara.ir URL taken from a search result. |
| platform_docsA | Collect the deployment documentation for one platform, ready to write a liara.json. Returns the platform's quick start, deployment and environment-variable pages plus the complete liara.json reference, so every key you write can be cited. Args: platform: The target platform, for example "django" or "nextjs". needs: Extra requirements to look up as well, such as "disk", "cron" or "websocket". At most 10 short items. |
| diagnose_logA | Extract the error from a failing build or runtime log and fetch the docs for it. Reduces the log to one error signature — the most specific failure line, not the last one — and returns the documentation pages explaining that class of failure. Args: log: The raw log text. Only the last 300 lines are read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Corpus provenance | Which documentation snapshot this server answers from, and how it searches. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: search, read a specific page, aggregate platform-specific docs, and diagnose logs. No overlap or ambiguity.
All tools use snake_case and mostly follow verb_noun (search_docs, read_page, diagnose_log), but platform_docs is a noun phrase rather than a verb, which is a minor deviation.
Four tools are well-scoped for a documentation server, covering search, retrieval, and specialized workflows without unnecessary bloat.
The core documentation lifecycle (search, read, platform-specific aggregation, and error diagnosis) is covered. Minor gaps like browsing an index or listing available platforms exist, but they are not critical.