Infimium MCP Server

Private context layer for AI agents: web, docs, code search, dep graph, memory, planning.

Local serverstdioPython

What is the Infimium MCP server?

If you already use Infimium, the infimium mcp server is the piece that lets your assistant work with it directly. Private context layer for AI agents: web, docs, code search, dep graph, memory, planning.

What the server does

The Private Context Layer & Super Brain for Your Codebase. Give AI agents persistent memory, deep dependency graphs, and instant code context -- 100% local, zero token bloat.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • hello_infimium — Confirms the MCP server is healthy
  • get_context — Loads tri-zonal YAML context: stable repo anchors, live Git/index state, and active execution
  • semantic_code_search — Finds code by meaning and returns symbol signatures first
  • expand_symbol — Loads one full implementation only when needed
  • query_local_docs — Searches local Markdown, text, HTML, and PDF files
  • dep_graph — Shows imports, callers, callees, and HTTP routes for a symbol
  • project_memory — Keeps active scratchpad events, compact milestones, and durable project rules across agents
  • plan — Builds a grounded implementation plan from code and graph context
  • web_search — Searches the web through optional Tinyfish configuration
  • fetch_url — Extracts readable Markdown or text from a URL
  • shell — Runs allowlisted commands with timeouts and output limits

Credentials and setup notes

Configuration is passed through the environment: SEARCH_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

infimium on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Infimium's toolset — hello_infimium, get_context, semantic_code_search and 8 more — is a fair guide to whether it matches your workflow. It is maintained by aryankumar06; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Infimium.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
hello_infimiumConfirms the MCP server is healthy.
get_contextLoads tri-zonal YAML context: stable repo anchors, live Git/index state, and active execution.
semantic_code_searchFinds code by meaning and returns symbol signatures first.
expand_symbolLoads one full implementation only when needed.
query_local_docsSearches local Markdown, text, HTML, and PDF files.
dep_graphShows imports, callers, callees, and HTTP routes for a symbol.
project_memoryKeeps active scratchpad events, compact milestones, and durable project rules across agents.
planBuilds a grounded implementation plan from code and graph context.
web_searchSearches the web through optional Tinyfish configuration.
fetch_urlExtracts readable Markdown or text from a URL.
shellRuns allowlisted commands with timeouts and output limits.

How to install the Infimium MCP server

{
  "mcpServers": {
    "infimium": {
      "command": "npx",
      "args": ["-y", "infimium"],
      "env": {
        "SEARCH_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SEARCH_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Infimium to hello infimium.
  • Use Infimium to get context.
  • Use Infimium to semantic code search.

Frequently asked questions

It connects Infimium to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (hello_infimium, get_context, semantic_code_search, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Infimium directly.