get_repository_info
Get information about an indexed repository including status and metadata
LABSCO 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
USE CASES
01
Getting oriented in a repository you did not write
Indexing happens once and answers come back with the code they point at, so the first question does not have to be a file search.
02
Tracing behaviour that crosses two repositories
When a client and a service are separate repos, the answer lives in neither one alone; the query takes both at once.
03
Following up on an answer without restating the context
A second question usually depends on the first. The session ID and previous messages carry that thread instead of repeating it.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
greptile_env_check
Check environment variable configuration and setup status
greptile_help
Get comprehensive help and usage examples for all Greptile MCP tools
index_repository
Index a repository to make it searchable for future queries
query_repository
Query repositories using natural language to get detailed answers with code references
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. greptile_env_check is not in the documentation. Run index_repository on a codebase before query_repository can answer anything about it.
Requires
- npx on PATH
- Node.js 18+
- GREPTILE_API_KEY in your environment
- GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx greptile-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"greptile": {
"command": "npx",
"args": [
"greptile-mcp-server"
],
"env": {
"GREPTILE_API_KEY": "<YOUR_GREPTILE_API_KEY>",
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
