Can I ask natural language questions about my codebase?

Yes! The `query_codebase` tool sends a natural language question along with repository references and returns AI-generated answers with specific code references (file paths and line numbers). For follow-up questions, use `query_with_context` with the session ID from the previous response to maintain conversation continuity.

Do I need to index my repository before querying it?

Yes. Use `index_repository` with the remote host (github or gitlab), repository path (owner/repo), and branch name. Check indexing progress with `get_repository_status`. Once indexed, you can query and search the repository. Use `reindex_repository` to refresh the index after significant code changes.

Can I search for specific code patterns across my repositories?

Yes. The `search_codebase` tool performs semantic search across your indexed repositories to find relevant files and functions. For targeted results, use `search_by_filepath` to narrow the search to a specific file path. Use `get_file_info` to retrieve indexed metadata for any file.

Greptile MCP Connector for Claude

A+

Search and understand any codebase instantly with AI that reads your repositories and answers technical questions accurately.

11 tools Official Updated Jun 28, 2026 Official Vinkius Partner

More Details Connect to Claude

Connect your Greptile account to any AI agent and unlock AI-powered codebase understanding through natural conversation.

What you can do

AI Codebase Q&A — Ask natural language questions about one or more repositories and receive AI-generated answers with code references
Contextual Follow-ups — Continue conversations with session context for multi-turn codebase exploration
Semantic Code Search — Search across indexed repositories to find relevant files, functions, and code patterns
File-Specific Search — Target searches within a specific file path for precise results
Repository Indexing — Submit GitHub or GitLab repositories for indexing, check progress, and trigger re-indexing
Repository Management — List all indexed repos, inspect file metadata, and remove outdated indexes
Usage Monitoring — Track API consumption and rate limits

How it works

Subscribe to this server
Enter your Greptile API Key from the developer dashboard
Start querying your codebase from Claude, Cursor, or any MCP-compatible client

Who is this for?

Developers — understand unfamiliar codebases, find implementations, and navigate large repositories through conversation
Code Reviewers — search for related patterns, understand code context, and trace dependencies
Engineering Managers — get quick answers about architecture decisions, coding patterns, and technical debt

codebase-intelligencesemantic-searchrepository-indexingnatural-language-querycode-understandingdeveloper-productivity

See how to talk to your AI agent using Greptile.

How does the authentication middleware work in our backend repository?

Based on your indexed repository 'github:main:company/backend-api', the authentication middleware is implemented in `src/middleware/auth.ts` (lines 12-48). It uses a JWT-based flow: 1) Extracts the Bearer token from the Authorization header (line 18). 2) Verifies the token signature using the RS256 algorithm with a public key from `config/keys.ts` (line 24). 3) Attaches the decoded user payload to `req.user` (line 32). 4) Falls through to a 401 handler if verification fails (line 41). The middleware is applied globally in `src/app.ts` line 15 via `app.use(authMiddleware)`. Would you like to search for how specific routes use this middleware?

Search for all files that import the database connection module and show me the file info.

Semantic search for 'database connection import' found 8 files: 1) `src/services/user-service.ts` — imports `db` from `../config/database`, 42 functions. 2) `src/services/order-service.ts` — imports `db`, 28 functions. 3) `src/repositories/user-repo.ts` — imports `pool` from database config, 15 functions. 4) `src/migrations/001-initial.ts` — direct pg import for schema setup. 5-8) Four test files importing the test database mock. File info for `src/config/database.ts`: 89 lines, exports `db` (Knex instance) and `pool` (pg Pool), last indexed 2 hours ago. Would you like to query how the connection pooling is configured?

Index our new frontend repository and check the indexing status.

Repository submitted for indexing! Remote: github, Repository: company/frontend-app, Branch: main. Current status: 'processing' — 45% complete (scanning 1,247 files). Estimated time remaining: 3 minutes. Indexed repositories: 3 total. 1) 'company/backend-api' (main, completed, 892 files). 2) 'company/shared-lib' (main, completed, 234 files). 3) 'company/frontend-app' (main, processing, 45%). Once completed, you'll be able to query and search the frontend codebase. Would you like to check again in a few minutes?

Related Connectors

Qualtrics MCP

15 tools Official

Automate survey management and data collection via Qualtrics — list surveys, manage distributions, and export responses directly from any AI agent.

A+ View details →

Sentry MCP

10 tools Official

Grant your AI agent full access to Sentry's Application Performance Monitoring tools to track raw exceptions, resolve error logs, and inspect crash stack traces dynamically.

A+ View details →

Wing Assistant MCP

6 tools Official

Manage your Wing virtual assistants and delegate tasks programmatically through AI.

A+ View details →

Dwolla MCP

30 tools Official

Automate payments and bank transfers via Dwolla — manage customers, funding sources, and initiate transfers directly from any AI agent.

A+ View details →