greptile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind to for SSE transport | 0.0.0.0 |
| PORT | No | Port for SSE transport | 8050 |
| DEBUG | No | Enable debug mode | false |
| LOG_LEVEL | No | Logging level | info |
| TRANSPORT | No | Transport method (sse or stdio) | sse |
| GITHUB_TOKEN | Yes | GitHub/GitLab Personal Access Token for repository access (required) | |
| GREPTILE_API_KEY | Yes | API key for accessing the Greptile API (required) | |
| GREPTILE_TIMEOUT | No | Timeout for Greptile API requests in seconds | 60.0 |
| GREPTILE_BASE_URL | No | Base URL for Greptile API | https://api.greptile.com/v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| greptile_helpA | Get comprehensive help and usage examples for all Greptile MCP tools |
| greptile_env_checkB | Check environment variable configuration and setup status |
| index_repositoryC | Index a repository to make it searchable for future queries |
| query_repositoryC | Query repositories using natural language to get detailed answers with code references |
| get_repository_infoC | Get information about an indexed repository including status and metadata |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| codebase_exploration | Start exploring a codebase with guided questions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Greptile MCP Help | Comprehensive documentation for all Greptile MCP features |
| Current Configuration | Current server configuration and settings |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap. get_repository_info retrieves metadata, greptile_env_check verifies setup, greptile_help provides documentation, index_repository prepares data, and query_repository performs searches. An agent can easily differentiate them.
The naming is mixed: three tools use a verb_noun pattern (get_repository_info, index_repository, query_repository), while two use a noun_verb pattern (greptile_env_check, greptile_help). This inconsistency is noticeable but still readable, as all names are descriptive and in snake_case.
With 5 tools, this server is well-scoped for its purpose of repository indexing and querying. Each tool earns its place by covering essential functions like setup, indexing, querying, and help, without being overly sparse or bloated.
The tool set covers the core workflow for a repository search service: environment setup, indexing, querying, and metadata retrieval, with a help tool for guidance. A minor gap is the lack of tools for managing indexed repositories (e.g., delete or update), but agents can work around this.