agentless-mcp

agentless-mcp

Enables coding agents to perform deterministic, model-free repository analysis and patch operations—tree-sitter repo maps, symbol/reference lookup, and SEARCH/REPLACE parsing/validation—via a CLI or MCP stdio server, without ever calling a language model.

Category
访问服务器

README

agentless-mcp

agentless-mcp is model-free structural machinery for coding agents: an on-demand tree-sitter repo map at any zoom level (directory tree, skeleton, line slice), symbol and reference lookup for bug localization, and deterministic patch parsing, syntax-checking and candidate validation. It never calls a language model — the calling agent supplies all the reasoning, and this tool supplies the parsing, ranking, containment and verification it would otherwise improvise. It ships as a CLI any agent can invoke over Bash and as a thin stdio MCP server over the same core.

Install

Today, from git:

uv tool install git+https://github.com/dmarlow-personal/agentless-mcp
agentless-mcp warmup

Add the mcp extra for the stdio server (uv tool install "agentless-mcp[mcp] @ git+..."). A PyPI release will follow; until then the git URL is the install route.

Status

Phases 1 through 6 are in. The CLI and the stdio MCP server are both live over one set of application services: repository map, directory tree, skeleton, slice, symbol lookup, symbol expansion, fan-in, location resolution, and the resolved-graph views — explain (one symbol's tiered fan-in and fan-out), path (shortest resolved path between two symbols) and cycles (module-level import cycles). The write side — SEARCH/REPLACE patch parsing, syntax checking, worktree-isolated apply, candidate validation and the equivalence-clustered vote — is CLI-only and never exposed over MCP.

Reference resolution is deterministic and model-free: a name is bound to its candidate definitions through the file's own imports and its own definitions, and every edge carries the discrete evidence tier behind it (same-file, resolved-via-import, unique, name-only-ambiguous). The graph is assembled in memory on every call from the current tree — nothing about it is stored, and there is no watcher.

Parsing happens on demand by default; agentless-mcp index builds a per-repository SQLite cache under $XDG_CACHE_HOME/agentless-mcp/ (never inside the analyzed repository) holding symbols, imports and references for files whose sha256 has not moved. Every answer's receipt names the cache generation and whether it is still the repository's own, and --no-cache / no_cache: true forces on-demand parsing.

A repository may declare its own defaults in an optional .agentless-mcp.json at its root (map budget, max files, granularity, docstrings, stoplist additions, and a test_cmd that only the CLI's validate will use, only when the invocation named none of its own, and only after printing it). The file is repository content: every value is schema-checked and bounded, no key is path-typed, and unknown keys are warnings in the response envelope rather than errors.

Start with docs/agent-guide.md: it is the usage guide written for the agent that will call this.

Development

uv sync --extra mcp
uv run agentless-mcp warmup
uv run pre-commit run --all-files
uv run pytest

uv run pre-commit run --all-files is the gate — it is a strict superset of running ruff by hand (it adds ruff-format, mypy strict, codespell, import-linter and deptry).

Windows support

Linux and macOS are the supported platforms: they are what the test suite runs on, and every guarantee below is asserted there. Windows is documented best effort — the POSIX-only calls have Windows paths, there is no Windows CI, and nothing here has been executed on Windows.

Covered:

  • The whole read surface. Map, tree, skeleton, slice, symbol lookup, fan-in and location resolution are pure parsing and path arithmetic, and paths go through pathlib with repository-relative results normalized to forward slashes.
  • The tag cache, including its single-writer discipline. The index lock is fcntl.flock on POSIX and msvcrt.locking on Windows, selected in util/filelock.py; both are non-blocking, so a second concurrent index run is refused rather than queued on either platform.
  • Patch parsing, syntax checking and the equivalence key.

Not covered, and the difference is real:

  • The timeout guarantee is weaker. On POSIX a timed-out test command has its whole process group killed (SIGTERM, then SIGKILL), so anything it spawned dies with it. On Windows the child is created with CREATE_NEW_PROCESS_GROUP and then terminate()/kill() is sent to the leader only: grandchildren can survive a timeout. If your test command starts a server, expect to clean it up yourself.
  • No Windows CI. The platform dispatch is unit-tested on Linux; the Windows system calls themselves are not exercised anywhere.
  • Anything depending on git worktree behaves as the local git does; it has not been exercised on Windows filesystems.

Security

The tool's posture toward an analyzed repository is read-only and path-confined: the MCP surface exposes read tools only, patch application and test execution are CLI-side and default to an isolated git worktree, and no cache or scratch state is written inside the repository under analysis.

One supply-chain caveat is worth stating up front. Grammars come from tree-sitter-language-pack, which downloads a prebuilt platform bundle on first use. Those bundles are SHA-256 verified against a release manifest, and a mismatch is a hard failure — but the manifest itself (parsers.json) is HTTPS-trusted rather than cryptographically signed. We accept that risk under exact release-version pinning: tree-sitter and tree-sitter-language-pack are pinned as a unit and move only through a reviewed bump. Fetching is confined to an explicit warmup step, and both the manifest URL and the cache directory are overridable for mirrored or air-gapped installs. See docs/supply-chain-audit.md for the full audit.

License

MIT — see LICENSE.

Parts of this package are derived from Agentless (MIT, Copyright (c) 2024 OpenAutoCoder): the line-slice primitives, the location grammar, the SEARCH/REPLACE edit format and its parser, and the candidate filter ladder and vote key. NOTICE names each file and reproduces the upstream license.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选