E
eren23/attocode
Codebase understanding for Codex, Claude Code, Cursor, and other MCP clients.
★ 17·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 17 ★ · eren23/attocode · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 17 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
eren23/attocode;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Attocode Intelligence
Excerpted from the repository README (abridged)
Codebase understanding for Codex, Claude Code, Cursor, and other MCP clients. Run it on your working tree, or connect a team to a self-hosted service that analyzes committed repositories.
The intelligence engine now lives in packages/code-intel and ships as attocode-code-intel, independently of the legacy coding agent. AST navigation and keyword search need no model API key. Local embedding search, graph analysis, and team hosting are optional extras.
## Get started from this checkout
Requires Python 3.12+ and Git.
sh
uv tool install ./packages/code-intel
cd /path/to/your/project
attocode-code-intel init --client all
attocode-code-intel doctor --client codex
Use --client claude or --client cursor to configure one client. init installs the MCP connection and managed agent instructions, preserving unrelated configuration. Restart your agent after installation. Project-level Codex configuration requires a trusted project; Claude Code may ask you to enable the project MCP server.
For an installation shared across repositories:
sh
attocode-code-intel init --global --client codex
attocode-code-intel doctor --global --client codex --project /path/to/repo
Global servers select the explicit workspace, an advertised MCP root, or the repository containing their working directory. If a client supplies multiple roots, the agent must select one. Cursor's automatic instruction file is project-scoped even when its server connection is global; run init --client cursor in each project where you want those rules.
The latest published release is on GitHub Releases
and PyPI, available with
uv tool install attocode-code-intel. CHANGELOG.md lists the changes in each release.
The source installation above uses this checkout.
## Everyday use
Ask your agent to start with bootstrap(task_hint="what you are changing"). It receives relevant code, structure, recalled knowledge, and index coverage within a token budget. Follow with symbol search, references, dependencies, impact analysis, and test suggestions. review_change reports structured findings and identifies failed analysis passes.
Local file watchers and per-operation filesystem checks pick up edits, new files, deletions, and import-only changes. With watching disabled, notify_file_changed offers an explicit refresh. Learnings persist in the existing .attocode/cache/memory.db, so different agents can reuse them. The full profile provides record_learning, recall, update_learning, and learning_feedback to maintain knowledge.
New installations and direct server invocations use the compact daily tool profile. init --profile full exposes the complete local catalog, including rules and security analysis, history, architecture, retrieval pins, snapshots, overlays, and cache maintenance. The shipped local lean profile is opt-in with init --profile lean; remote profiles remain daily and full. capabilities reports the actual catalog and optional enhancements.
The change investigation workflow
(attocode-code-intel changes) combines a Git diff with changed definitions,
caller evidence, import impact and candidate tests. attocode-code-intel trace
follows static caller paths. You can export JSON/Markdown, check saved evidence
The intelligence engine now lives in packages/code-intel and ships as attocode-code-intel, independently of the legacy coding agent. AST navigation and keyword search need no model API key. Local embedding search, graph analysis, and team hosting are optional extras.
## Get started from this checkout
Requires Python 3.12+ and Git.
sh
uv tool install ./packages/code-intel
cd /path/to/your/project
attocode-code-intel init --client all
attocode-code-intel doctor --client codex
Use --client claude or --client cursor to configure one client. init installs the MCP connection and managed agent instructions, preserving unrelated configuration. Restart your agent after installation. Project-level Codex configuration requires a trusted project; Claude Code may ask you to enable the project MCP server.
For an installation shared across repositories:
sh
attocode-code-intel init --global --client codex
attocode-code-intel doctor --global --client codex --project /path/to/repo
Global servers select the explicit workspace, an advertised MCP root, or the repository containing their working directory. If a client supplies multiple roots, the agent must select one. Cursor's automatic instruction file is project-scoped even when its server connection is global; run init --client cursor in each project where you want those rules.
The latest published release is on GitHub Releases
and PyPI, available with
uv tool install attocode-code-intel. CHANGELOG.md lists the changes in each release.
The source installation above uses this checkout.
## Everyday use
Ask your agent to start with bootstrap(task_hint="what you are changing"). It receives relevant code, structure, recalled knowledge, and index coverage within a token budget. Follow with symbol search, references, dependencies, impact analysis, and test suggestions. review_change reports structured findings and identifies failed analysis passes.
Local file watchers and per-operation filesystem checks pick up edits, new files, deletions, and import-only changes. With watching disabled, notify_file_changed offers an explicit refresh. Learnings persist in the existing .attocode/cache/memory.db, so different agents can reuse them. The full profile provides record_learning, recall, update_learning, and learning_feedback to maintain knowledge.
New installations and direct server invocations use the compact daily tool profile. init --profile full exposes the complete local catalog, including rules and security analysis, history, architecture, retrieval pins, snapshots, overlays, and cache maintenance. The shipped local lean profile is opt-in with init --profile lean; remote profiles remain daily and full. capabilities reports the actual catalog and optional enhancements.
The change investigation workflow
(attocode-code-intel changes) combines a Git diff with changed definitions,
caller evidence, import impact and candidate tests. attocode-code-intel trace
follows static caller paths. You can export JSON/Markdown, check saved evidence
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/eren23-attocode/)
- Source
- awesome · https://github.com/eren23/attocode
- Browse by field
- MCP servers
- Traction
- 17 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.