Portable MCP code-map server for token-efficient coding agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-ntc-road-map-codex-agent","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ntc-code-map **Portable MCP code-map server for token-efficient coding agents.** `ntc-code-map` builds a lightweight index of your repository's files and symbols, then serves a compact, task-aware code map over the [Model Context Protocol (MCP)](https://modelcontextprotocol.io). Coding agents like [Codex](https://openai.com/codex) use it to understand project structure **before** reading files — saving thousands of tokens per session. ## Why? LLM coding agents waste tokens on broad `grep`, `find`, and full-file reads to orient themselves. `ntc-code-map` compresses this into a single ranked map call: | Without ntc-code-map | With ntc-code-map | |---|---| | Agent reads 10+ files to understand structure | Agent gets a ranked map in ~3500 tokens | | Broad `grep -R`, `tree`, `ls -R` | One `repo_map(task)` call | | No symbol awareness | Symbol-level navigation + references | ## Quick Start ### 1. Install ```bash pip install mcp-ntc-road-map-codex-agent ``` ### 2. Initialize in your project ```bash cd your-project # Create config ntc-code-map init # Build the index ntc-code-map index # Check status ntc-code-map status ``` ### 3. Use with Codex ```bash # Auto-configure Codex MCP integration ntc-code-map init-codex # Auto-inject workflow into AGENTS.md ntc-code-map init-agents ``` That's it! Codex will now use `ntc-code-map` automatically. ## MCP Tools When running as an MCP server, these tools are available: | Tool | Description | |---|---| | `index_status` | Check if the repo index exists and is fresh | | `index_repo` | Build/rebuild the SQLite index | | `repo_map` | Task-aware ranked map of relevant files + symbols | | `find_symbols` | Search symbols by name, kind, scope, signature | | `find_files` | Search files by path and content | | `module_map` | Compact map for a specific file or directory | ### Recommended agent workflow ``` 1. index_status → is the index fresh? 2. index_repo → rebuild if stale 3. repo_map(task) → get ranked contex…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.