Developer Tools & Devops · Greptile MCP + Claude
Greptile MCP with Claude: Faster Code Search and Pull Request Review
The short answer
Claude works with Greptile through the Model Context Protocol, an open standard that lets Claude securely use software with permissions the organisation controls. Once connected, Claude can search indexed codebases, inspect pull requests and reviews, manage custom context, and answer questions about engineering knowledge in natural language.
What is Greptile MCP?
Greptile is a developer platform that indexes codebases, pull requests and engineering knowledge. It helps teams find code quickly, review changes and keep reusable project context in one place. Software engineers, engineering managers, platform teams and technical leads typically use it to understand large or unfamiliar code and to keep reviews consistent across projects.
How Claude connects to Greptile MCP through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool such as Greptile securely, reading information and taking actions within permissions that your organisation sets. Claude does not gain access beyond what you approve.
Once connected through Greptile's MCP server, Claude can typically search across connected codebases, look at specific pull requests and their review comments, and work with the custom context your team has stored. Engineers can ask questions such as where a feature is handled or what a recent change affected, without writing search queries by hand.
Access is granted through the sign-in method Greptile supports, Dynamic Client Registration with OAuth, and is limited to the least access needed for each role. Sensitive actions can require a person's approval before they run, and every interaction can be logged so your team can see what was done and when.
What you can automate
Finding code across large repositories
Engineers often spend hours tracing how a function, service or configuration works. With Claude connected to Greptile, they can ask in plain English where a behaviour is implemented and receive relevant locations and explanations. New joiners benefit most, because they can learn a system without relying on a senior colleague's time for every question.
Supporting pull request reviews
Review queues slow down delivery. Claude can read a pull request and its existing review history through Greptile, summarise what changed and highlight areas that may need closer attention. Reviewers still make the decision, but they start with a clearer picture and spend less time on routine checks.
Keeping project context current
Teams often hold coding standards and architecture decisions in old documents that no one reads. Through Greptile's custom context features, Claude can help store and retrieve these rules so answers and reviews reflect current team practice. Managers can review and update this context as standards change.
Analysing engineering knowledge bases
Engineering leaders frequently need to know which parts of a system carry the most risk or where knowledge is concentrated in one person. Claude can help analyse the indexed knowledge base and summarise patterns, giving leaders a starting point for planning reviews, training and staffing decisions.
Onboarding and internal support
Support engineers and platform teams answer the same questions repeatedly. A Claude assistant connected to Greptile can handle first-line questions about how a system works, and pass complex cases to a human engineer with the relevant code references attached.
An end-to-end workflow: Pull request triage with context and ticket updates
TriggerA new pull request is opened against a core service repository.
Claude retrieves the pull request and its changed files through Greptile.
Claude checks the reusable project context for relevant coding standards and flags any departures.
Claude summarises the change and notes which related code paths may be affected.
The summary is posted to the reviewer and a linked ticket in the team's project management system, with a note for a human to confirm priority.
A senior engineer approves the final review decision before any merge action is taken.
OutcomeReviewers start each pull request with a consistent summary and a checklist of standards, which typically shortens time to first review and keeps decisions with the engineering team.
How we set it up
Free automation audit
We review how your engineering team searches code, runs reviews and shares standards, and identify the workflows where Greptile and Claude would save the most time.
Secure connection
We connect Claude to Greptile using its supported Dynamic Client Registration with OAuth sign-in, with least-privilege access scoped to the repositories and actions each role needs.
Workflow design
We design the end-to-end process across Greptile and your other systems, such as Microsoft 365, your ticketing tool or your source control platform, with approval points for consequential actions.
Testing against real cases
We test the workflow against past pull requests and real search questions from your team, adjusting context and permissions until results meet your standards.
Launch and training
We launch with monitoring and audit logs turned on, then train your engineers, leads and support staff to use the assistant well and to know when to escalate.
Who benefits
- Engineering managers
- Clearer review throughput and consistent standards across teams.
- Software engineers
- Faster answers about unfamiliar code and less time spent tracing systems by hand.
- Platform and DevOps leads
- Better visibility into codebase knowledge and fewer repeated support questions.
- CTOs and technical directors
- Stronger knowledge retention when people change roles or leave.
Security and control
- Least-privilege access so Claude sees only the repositories and actions approved for each user.
- Human approval before any consequential action, such as merging or changing shared settings.
- Audit logs of every interaction, so engineering leaders can review what was accessed and changed.
- Regular checks of custom context to remove outdated standards and prevent wrong guidance.
- Testing against real past cases before launch to confirm the assistant behaves as expected.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with their data handling policies. Companies in India should consider the Digital Personal Data Protection Act, 2023, when code or personal data is processed. Organisations in the UAE and Saudi Arabia must meet local data protection laws, and we select the hosting region to help meet these requirements in each case. Hosting location is agreed during the audit.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Greptile MCP server do?
The Greptile MCP server acts as a secure bridge between AI tools such as Claude and Greptile's platform. It lets approved assistants search indexed codebases, inspect pull requests and reviews, manage custom context and query engineering knowledge in natural language, within the permissions you set.
Is connecting Greptile to Claude secure?
Security depends on how the connection is configured. Greptile supports Dynamic Client Registration with OAuth, and we apply least-privilege access, approval points for consequential actions and audit logging. Your team keeps control over which repositories and actions are available to each user.
What can Claude do with Greptile once connected?
Typically, Claude can search connected codebases, read pull requests and their reviews, work with your custom context and analyse engineering knowledge. It can summarise findings and draft outputs, but sensitive actions are designed to wait for a person's approval.
How long does setup take?
Timelines depend on the number of repositories, the workflows chosen and how many systems need to be connected. A focused connection and a single workflow can often be launched within a few weeks, following the free automation audit, testing and training stages.
Which plan or permissions do I need?
In general, you need an active Greptile account with access to the repositories and features you want Claude to use, plus the authority to approve the OAuth connection. Your administrator can confirm the exact access level during the audit, and we set permissions to the minimum required.