Get started

Greptile for AI agents

Greptile lets teams search connected codebases in natural language and inspect pull requests, reviews, and engineering knowledge. Developers wire it into their own apps and internal tools instead of building the underlying capability from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect GreptileSee the 21 actions ↓
Developer toolsOAuth 2.0 (MCP)MCP + RESTgreptile.com
AUDIT LOG · GREPTILEPOLICY: acme-support
09:41:07 · claude · u_8f2read
greptile.list_code_reviews
List code reviews✓ allowed · 212ms
09:41:08 · claude · u_8f2read
greptile.get_me
Get me✓ allowed · 164ms
09:41:09 · claude · u_8f2write
greptile.create_custom_context
Create custom context✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
greptile.get_merge_request
Get merge request✕ blocked · policy: deny
EVERY GREPTILE CALL, ON THE RECORD
01 · USE CASES

What agents do in Greptile.

01

Search a codebase for a pattern

Search a connected repository for where a specific function or config value is used.

02

Pull a code review's findings

Fetch an existing code review's comments to summarize what a reviewer flagged.

03

Trigger a review on a pull request

Trigger an automated code review on a new pull request so findings are ready before a human looks.

02 · ACTIONS

21 Greptile actions, graded by risk.

Every Greptile action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

16

Look things up. Allowed by default.

  • greptile.get_me
    Get me
  • greptile.get_code_review
    Get code review
  • greptile.list_code_reviews
    List code reviews
  • greptile.list_repositories
    List repositories
  • greptile.get_custom_context
    Get custom context
  • greptile.list_pull_requests
    List pull requests
  • greptile.list_custom_context
    List custom context
  • greptile.list_knowledge_bases
    List knowledge bases
  • greptile.search_custom_context
    Search custom context
  • greptile.search_knowledge_base
    Search knowledge base
  • greptile.get_analytics_overview
    Get analytics overview
  • greptile.list_analytics_findings
    List analytics findings
  • greptile.search_greptile_comments
    Search greptile comments
  • greptile.get_knowledge_base_document
    Get knowledge base document
  • greptile.list_analytics_filter_options
    List analytics filter options
  • greptile.list_knowledge_base_documents
    List knowledge base documents

write

2

Create and change things. Allow, or ask the user first.

  • greptile.create_custom_context
    Create custom context
  • greptile.trigger_code_review
    Trigger code review

destructive

3

Delete, cancel or archive. Ask first, or deny outright.

  • greptile.get_merge_request
    Get merge request
  • greptile.list_merge_requests
    List merge requests
  • greptile.list_merge_request_comments
    List merge request comments
03 · HOW IT WORKS

Greptile in three steps.

  1. 01Your users connect GreptileThey sign in to Greptile on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create custom context” can wait for the user, and “get merge request” can be denied outright.
  3. 03Any agent can actYour agent calls Greptile through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('greptile', {
  read: 'allow',
  write: 'ask',        // create_custom_context
  destructive: 'deny',  // get_merge_request
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Greptile connects.

Greptile runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Greptile through the same endpoint, policies and audit log as every other app.

The same Greptile connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 (MCP)
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Greptile from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Greptile and Arc0, answered.

Q01

Can I use Greptile with Claude, ChatGPT or Cursor?

Yes. Connect Greptile to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Greptile actions you allow.

Q02

How do users connect Greptile?

Greptile runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Greptile through the same endpoint, policies and audit log as every other app.

Q03

Which Greptile actions can my agent take?

21 in total: 16 read, 2 write and 3 destructive, such as “create custom context”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Greptile?

Yes. Actions like “get merge request” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Greptile too?

Yes. The same Greptile connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Greptile into your agent.

Your users connect Greptile once, under your brand. Your agent gets 21 actions behind your policies, with every call on the record.

Connect GreptileBrowse all apps →

Free to build · MCP + REST · Audit log on every plan