Ontomics
Point an MCP server at a local repo so coding agents pull domain concepts without stuffing whole trees into every turn.
Overview
Ontomics is a MCP server for the Build phase that indexes a repository's domain knowledge so agents retrieve structured context with far less token overhead.
What is this MCP server?
- stdio MCP via npx @ontomics/ontomics with required --repo filepath argument
- Indexes domain knowledge from the repository you pass on startup
- Marketed as ~20× fewer tokens and ~10× faster context vs naive full-repo reads
- npm registry package version 0.3.1, transport type stdio
- GitHub source at EtienneChollet/ontomics for updates and issue tracking
- Server schema version 0.3.1
- Single npm package @ontomics/ontomics with stdio transport
- One required named CLI argument: --repo (filepath)
Community signal: 34 GitHub stars.
What problem does it solve?
Agents keep re-reading the same codebase and still miss how domain concepts connect across modules, which burns tokens and slows every coding session.
Who is it for?
Indie builders on large or domain-heavy repos who want Claude Code or Cursor to stay accurate without maxing context windows.
Skip if: Greenfield repos with almost no code yet, or teams that only need one-off file reads without persistent indexing.
What do I get? / Deliverables
After you register ontomics with --repo set, the agent can query a domain index instead of loading huge slices of the tree into each prompt.
- Running stdio MCP server bound to the chosen repository
- Queryable domain-knowledge index for agent tool calls during coding
- Leaner agent context workflow versus ad-hoc full-tree reads
Recommended MCP Servers
Journey fit
Ontomics runs during active product work when the agent needs accurate, repo-specific context while you build features. It is agent infrastructure: a stdio MCP index wired into Claude Code, Cursor, or Codex—not a standalone app feature.
How it compares
Repo domain index MCP server, not a generic web-search or documentation scraper skill.
Common Questions / FAQ
Who is Ontomics for?
Solo and indie developers using MCP-enabled coding agents who want faster, leaner context from an existing local repository.
When should I use Ontomics?
Use it during Build when you are implementing or refactoring in a non-trivial codebase and context size is slowing the agent down.
How do I add Ontomics to my agent?
Add a stdio MCP entry that runs npx @Ontomics/Ontomics with --repo pointing at your project path, then restart Claude Code, Cursor, or your MCP client.