Developer Tools

greptile.com

Manages merge requests and custom context for code review workflows.

1 endpoint16 known toolsFirst detected May 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.greptile.com/mcp

No auth detected

MCP server metadata

Name: Greptile MCP Server
Version: 1.0.0

Capabilities

tools

Known tools 16

list_custom_context

List organization custom context with optional filtering by type and generation source

Inferred read-only

get_custom_context

Get detailed custom context information including evidence and linked comments.

Inferred read-only

search_custom_context

Search custom context by content using text search

Inferred read-only

list_merge_requests

List merge requests/PRs.

Inferred read-only

list_pull_requests

List pull requests (alias for list_merge_requests).

Inferred read-only

get_merge_request

Get detailed merge request information including metadata, statistics, Greptile comments, and review analysis.

Inferred read-only

list_merge_request_comments

Get all comments for a PR including Greptile review comments (clearly marked with sourceType), human comments, and other bot comments.

Inferred read-only

list_code_reviews

List code reviews with optional filtering by repository and status.

Inferred read-only

get_code_review

Get detailed code review information including body, status, summary citations, and customer-provided review metadata (branch, baseSha, headSha, changedFiles, instructions, strictness, correlationId; keys absent from a review are omitted).

Inferred read-only

trigger_code_review

Trigger a code review for a pull request/merge request.

Inferred read-only

search_greptile_comments

Search specifically for Greptile review comments across all merge requests.

Inferred read-only

create_custom_context

Create a new custom context for an organization

Potential side effects

list_knowledge_bases

List the repositories in your organization that Greptile holds knowledge base data for — the per-repository documentation Greptile synthesizes from the codebase and consults while reviewing.

Inferred read-only

list_knowledge_base_documents

List the document paths in one repository's current published knowledge base.

Inferred read-only

get_knowledge_base_document

Get the markdown body of a single knowledge base document.

Inferred read-only

search_knowledge_base

Case-insensitive substring search across one repository's knowledge base.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.greptile-mcp-server]
url = "https://api.greptile.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "greptile-mcp-server": {
      "type": "http",
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: greptile-mcp-server
Remote MCP URL: https://api.greptile.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "greptile-mcp-server": {
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "greptile-mcp-server": {
      "type": "http",
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "greptile-mcp-server",
  "transport": "streamable-http",
  "url": "https://api.greptile.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.