infimium
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARCH_API_KEY | No | API key for the search provider (e.g., Tinyfish). | |
| SEARCH_PROVIDER | No | Optional search provider (e.g., tinyfish). Required only if web_search is used. | |
| INFIMIUM_TELEMETRY | No | Set to 'false' to disable anonymous telemetry. | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_infimiumB | Health probe for the Infimium MCP server. |
| web_searchC | Search the web for current information. |
| fetch_urlC | Fetch a URL and extract readable content. |
| query_local_docsC | Query indexed local documentation. |
| semantic_code_searchC | Search code semantically and return compact symbol signatures. |
| expand_symbolB | Load the full implementation of one symbol returned by semantic_code_search. |
| dep_graphC | Inspect dependency relationships for a symbol. |
| shellC | Run an allowlisted shell command. |
| planC | Generate a grounded implementation plan for the current repository. |
| project_memoryB | Manage compact project memory across chats, agents, and IDEs: remember active work, complete and archive sessions, search history, or update durable rules. |
| get_contextA | Read the balanced YAML context layer with repo overview, Git state, task, memory, and AST-first handoff guidance. Pass project_path once to activate the current IDE workspace as the default. |
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 11 tools
Each tool targets a clearly distinct function: context reading, health probe, web search, URL fetching, local docs, semantic code search, symbol expansion, dependency graph, shell execution, planning, and project memory. There is no overlap or ambiguity between them.
Naming is inconsistent: some tools use verb_noun (web_search, fetch_url, expand_symbol), while others are bare nouns (shell, plan), abbreviations (dep_graph), or greetings (hello_infimium). This mixed style makes the set harder to predict and navigate.
With 11 tools, the server is well-scoped—each tool earns its place and the count is within the ideal 3-15 range. It feels comprehensive without being bloated.
The tool surface covers a broad workflow: context, code exploration, web/docs lookup, shell access, planning, and memory. Slight gaps like a direct file editor exist, but shell can fill in, so the coverage is nearly complete.