---
title: "Greptile MCP integration for LuumenAI"
url: "https://www.luumen.ai/integrations/greptile-mcp/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Greptile MCP integration for LuumenAI

Search code, read reviews, and add review rules that stick across repositories.

## What LuumenAI can do with Greptile MCP

LuumenAI connects to Greptile MCP with OAuth 2.0 and exposes 21 tools (19 read-only · 1 write · 1 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: OAuth 2.0
- Tools available: 21 tools (19 read-only · 1 write · 1 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: AI & automation

## About Greptile MCP with LuumenAI

Connect Greptile MCP and your agent can read the engineering context behind a change: code-review runs, pull request history, review findings by repository or author, and published knowledge-base documents. When a recurring review comment should become a standing rule, the agent drafts it and holds the write for your approval. Luumen authenticates with OAuth dynamic client registration.

## Example tools

Read-only (19 in total):

- `GREPTILE_MCP_GET_ANALYTICS_OVERVIEW` — Get review analytics for repositories visible to the caller, optionally intersected by exact team, repository, and author filters.
- `GREPTILE_MCP_GET_CODE_REVIEW` — Get one code-review run by its stable id.
- `GREPTILE_MCP_GET_CUSTOM_CONTEXT` — Get one saved review rule or pattern and up to 10 linked review-comment references.
- `GREPTILE_MCP_GET_KNOWLEDGE_BASE_DOCUMENT` — Read one current knowledge-base markdown document after listing its path.
- `GREPTILE_MCP_GET_ME` — Identify the caller and discover the organizations available to other tools.
- `GREPTILE_MCP_GET_MERGE_REQUEST` — Get one pull request or merge request with metadata, statistics, comments, up to 10 recent review records, and summary citations for the latest completed review.
- `GREPTILE_MCP_LIST_ANALYTICS_FILTER_OPTIONS` — List exact team names, repository names, or author logins available to the caller for analytics filters.
- `GREPTILE_MCP_LIST_ANALYTICS_FINDINGS` — List review findings visible to the caller, newest first, with optional exact scope, severity, security, stored-addressed-status, text, and date filters.

Write and destructive (2 in total, subject to configured approval policy):

- `GREPTILE_MCP_CREATE_CUSTOM_CONTEXT` — Create a persistent review rule or pattern in the selected organization.
- `GREPTILE_MCP_TRIGGER_CODE_REVIEW` — Request a new asynchronous Greptile review for an existing GitHub pull request or GitLab merge request.

## Frequently asked questions

### How does LuumenAI connect to Greptile MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Greptile MCP on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to Greptile MCP — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/greptile-mcp/