AI coding agents spend most of their token budget *finding* code before they can *work on* it. They grep, read files, grep again, backtrack. On a
Most file and storage access work still happens through a UI a human drives. Codeix MCP server moves it into the conversation instead. AI coding agents spend most of their token budget finding code before they can work on it. They grep, read files, grep again, backtrack. On a large codebase the agent might burn thousands of tokens just locating the right function — or.
The server publishes 8 tools. What each one is for:
Problem — What happens todayexplore — Explore project structure: metadata, subprojects, files grouped by directorysearch — Unified full-text search across symbols, files, and texts (FTS5, BM25-ranked) with scope/kind/path/project filtersget_file_symbols — List all symbols in a fileget_children — Get children of a class/moduleget_callers — Find all places that call or reference a symbolget_callees — Find all symbols that a function/method callsflush_index — Flush pending index changes to diskInstallation goes through your MCP client rather than a global install: point it at codeix on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Codeix's toolset — Problem, explore, search and 5 more — is a fair guide to whether it matches your workflow. It is maintained by montanetech; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Codeix's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Problem | What happens today |
| explore | Explore project structure: metadata, subprojects, files grouped by directory |
| search | Unified full-text search across symbols, files, and texts (FTS5, BM25-ranked) with scope/kind/path/project filters |
| get_file_symbols | List all symbols in a file |
| get_children | Get children of a class/module |
| get_callers | Find all places that call or reference a symbol |
| get_callees | Find all symbols that a function/method calls |
| flush_index | Flush pending index changes to disk |
{
"mcpServers": {
"codeix": {
"command": "npx",
"args": ["-y", "codeix"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.