Skip to content

Connectors · Developer & infrastructure

Greptile MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Greptile and the rest of your systems. It gives your agent 21 Greptile actions (19 reads and 2 writes) and holds the Greptile credential itself, so the agent never does. It paces Greptile's limits and records every call. Connecting Greptile needs your own Greptile OAuth app and one admin sign-in.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "greptile.repositories.list",  intent: "check which Greptile account is connected"}# List repositories · read · 1 upstream call
  • 21actionsin one signed file
  • 19readlook, never change
  • 2writecreate and update
  • 0wait for a yesdestructive, confirmed first

Set up

Connect Greptile in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Greptile.

    OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Greptile, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.

    Before the first sign-in, Greptile needs an OAuth app of your own, registered in its developer portal. actionlake has no Greptile app to lend you.

    • access_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idOAuth client id from Greptile's dynamic client registration (POST https://auth.greptile.com/oauth2/register with…
    • client_secretYour OAuth app's client secret
    account { op: "connections.requirements", service: "greptile" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "greptile.repositories.list" }# list repositories · read · 1 upstream callcheck { action: "greptile.code_reviews.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Greptile at a glance

Sign-in
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Greptile, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide
access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to
60 calls a minute, per connection
API covered
Greptile (AI code review: pull requests, code reviews, review comments, custom context, knowledge base, analytics) API Greptile MCP Server 1.0.0 (https://api.greptile.com/mcp, MCP 2025-03-26)api.greptile.com
Built from
Greptile's documentation, read 23 October 2026api.greptile.comgreptile.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
19 of 19 reads, for up to 5 minutes; a write clears what it affects
Shared entities
3, so ask can line Greptile up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Greptile.

21 actions in 13 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 19readlook, never change
  • 2writecreate and update
  • 0destructivewait for a confirmation
  1. Custom contexts

    4

    3 read · 1 write · 0 destructive

    Create custom context · List custom context · Search custom context · Get custom context

  2. Code reviews

    3

    2 read · 1 write · 0 destructive

    Trigger code review · List code reviews · Get code review

  3. Knowledge base documents

    2

    2 read · 0 write · 0 destructive

    List knowledge base documents · Get knowledge base document

  4. Knowledge bases

    2

    2 read · 0 write · 0 destructive

    List knowledge bases · Search knowledge base

  5. Merge requests

    2

    2 read · 0 write · 0 destructive

    List merge requests · Get merge request

  6. Analytics filter options

    1

    1 read · 0 write · 0 destructive

    List analytics filter options

  7. Analytics findings

    1

    1 read · 0 write · 0 destructive

    List analytics findings

  8. Analytics overview

    1

    1 read · 0 write · 0 destructive

    Get analytics overview

5 more areas · 5 actions
  • Comments 1
  • Me 1
  • Merge request comments 1
  • Pull requests 1
  • Repositories 1

Top actions

The Greptile API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of Greptile's 5 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
greptile.repositories.listList repositoriesList repositories visible to the caller in the selected organization, sorted by name.readdevops.repository.list28 connectors
greptile.pull_requests.listList pull requestsAlias of list_merge_requests with the same filters and result contract.readdevops.pull_request.list12 connectors
greptile.merge_request_comments.listList merge request commentsList all matching comments for one pull request or merge request, newest first.readdevops.pull_request_comment.list5 connectors
greptile.code_reviews.createTrigger code reviewRequest a new asynchronous Greptile review for an existing GitHub pull request or GitLab merge request.writedevops.pull_request_review.create7 connectors
greptile.code_reviews.listList code reviewsList code-review runs visible to the caller, newest first, optionally filtered by repository, PR number, or status.readdevops.pull_request_review.list6 connectors
greptile.comments.searchSearch Greptile commentsSearch Greptile-generated review comments by case-insensitive body substring across PR and CLI/headless reviews, newest first.readthis connector
greptile.merge_requests.listList merge requestsList merge requests and pull requests visible to the caller, newest first.readthis connector
greptile.custom_contexts.listList custom contextList saved review rules and learned patterns visible to the caller, newest first.readthis connector
greptile.knowledge_bases.listList knowledge basesDiscover repositories with reachable Greptile knowledge-base data; start here before asking how an unfamiliar repository works.readthis connector
greptile.custom_contexts.createCreate custom contextCreate a persistent review rule or pattern in the selected organization.writethis connector
greptile.knowledge_bases.searchSearch knowledge baseSearch one repository's current knowledge base for a case-insensitive substring when you know the term, symbol, endpoint, or convention to investigate.readthis connector
greptile.analytics_findings.listList analytics findingsList review findings visible to the caller, newest first, with optional exact scope, severity, security, stored-addressed-status, text, and date filters.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Greptile actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Greptile pull requests have waited longest for a review?

    callsgreptile.pull_requests.list

  2. Writewrite

    Trigger code review in Greptile. Show me exactly what you will send before you save it.

    callsgreptile.code_reviews.create

Governance for Greptile

Every write can wait for a yes.

None of Greptile's actions is destructive. A key can still be held to reads, capped, and set so a person confirms every write.

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

a key for this connector
account {  op: "keys.create", name: "greptile-agent",  allowed_actions: ["greptile.*"], cap_calls: 2000,  confirm_policy: "human_for_writes"}
Illustrative. Scoped to Greptile only, capped at 2,000 upstream calls, every write confirmed.

Cost

What Greptile costs on actionlake.

Every Greptile action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Greptile refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 21 Greptile actions
  • 21actions pageeach page of a long list is one call
  • 19reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Greptile action.

21 actions by area: the id your agent calls, what it does, and its effect.

Custom contexts4
  • greptile.custom_contexts.createCreate custom contextwrite
  • greptile.custom_contexts.getGet custom contextread
  • greptile.custom_contexts.listList custom contextread
  • greptile.custom_contexts.searchSearch custom contextread
Code reviews3
  • greptile.code_reviews.createTrigger code reviewwrite
  • greptile.code_reviews.getGet code reviewread
  • greptile.code_reviews.listList code reviewsread
Knowledge base documents2
  • greptile.knowledge_base_documents.getGet knowledge base documentread
  • greptile.knowledge_base_documents.listList knowledge base documentsread
Knowledge bases2
  • greptile.knowledge_bases.listList knowledge basesread
  • greptile.knowledge_bases.searchSearch knowledge baseread
Merge requests2
  • greptile.merge_requests.getGet merge requestread
  • greptile.merge_requests.listList merge requestsread
Analytics filter options1
  • greptile.analytics_filter_options.listList analytics filter optionsread
Analytics findings1
  • greptile.analytics_findings.listList analytics findingsread
Analytics overview1
  • greptile.analytics_overview.getGet analytics overviewread
Comments1
  • greptile.comments.searchSearch Greptile commentsread
Me1
  • greptile.me.getGet caller and organizationsread
Merge request comments1
  • greptile.merge_request_comments.listList merge request commentsread
Pull requests1
  • greptile.pull_requests.listList pull requestsread
Repositories1
  • greptile.repositories.listList repositoriesread

Questions

The Greptile MCP server, answered.

Is there a Greptile MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 21 Greptile actions across custom contexts, code reviews, knowledge base documents and knowledge bases, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Greptile.

What do I need to connect Greptile?

Your own Greptile OAuth app, registered with Greptile (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Greptile app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "greptile" } lists exactly what to paste.

Can an AI agent change things in Greptile?

Only if its key allows it. 2 Greptile actions write, and none is destructive. A key can be limited to reads, capped, and set so a person confirms every write.

Will an AI agent use up my Greptile API limit?

actionlake paces every call to the limits in the Greptile service file: 60 calls a minute per connection. Repeated reads are answered from cache (19 Greptile actions can be), which never reaches Greptile.

What does a Greptile action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (21 Greptile actions page). Cache hits, searches, dry runs and calls Greptile refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Greptile API does it cover?

The Greptile (AI code review: pull requests, code reviews, review comments, custom context, knowledge base, analytics) API Greptile MCP Server 1.0.0 (https://api.greptile.com/mcp, MCP 2025-03-26) at api.greptile.com. It is built from Greptile's documentation as read on 23 October 2026. 21 actions in 13 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Greptile data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Greptile credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Greptile today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.