Summary
Questions about an unfamiliar codebase are answered against the indexed code, with the references included.
Indexing is a separate step from asking, so a repository is prepared once and queried many times — and get_repository_info is what tells you whether it is ready, rather than an empty answer. query_repository takes a list of repositories rather than one, which is what makes a question spanning two services answerable at all. Passing a session ID with previous messages keeps a line of questioning coherent instead of restating context each turn.
What it is
A client for Greptile's code search: index a repository on a branch, then query it conversationally.
What you get
- Repository indexing for a chosen branch and remote, with a forced reload when the index has drifted and an optional notification.
- Natural-language questions answered with code references, across one repository or several at once.
- Continuity across turns through a session ID and previous messages, with streaming, a genius mode and a timeout of your choosing.
- Index status and metadata for a repository, and a check on how the environment is configured.
Requirements
A Greptile API key in GREPTILE_API_KEY and a GitHub token in GITHUB_TOKEN.
Setup effort
One command plus a key — npx greptile-mcp-server, then supply credentials