AI & ML21 toolsBrowser login (OAuth), no API keys
Greptile integration for AI agents
Greptile MCP lets authorized agents search connected codebases, inspect pull requests and code reviews, manage custom context, and analyze engineering knowledge bases.
Use it from your agent
One ClawLink account serves every agent you run. Pick the guide for yours, or connect Greptile once and call the same tools from all of them.
Greptile for OpenClawInstall, pair, connect, first prompt
Greptile for Hermes AgentInstall, pair, connect, first promptMCPClaude Code, Cursor, any MCP clientCLI login or the remote MCP serverSetup
Connect Greptile through ClawLink's hosted setup.
- Auth: Browser login (OAuth), no API keys. The credential stays on the ClawLink server; your agent holds only a ClawLink key you can revoke.
- Where: the ClawLink dashboard, or ask your agent to connect it.
What your agent can do
Greptile exposes 21 tools through ClawLink.
| Tool | What it does | Kind |
|---|---|---|
greptile_mcp_get_analytics_overview | Get review analytics for repositories visible to the caller, optionally intersected by exact | Read |
greptile_mcp_get_code_review | Get one code-review run by its stable id | Read |
greptile_mcp_get_custom_context | Get one saved review rule or pattern and up to 10 linked review-comment references | Read |
greptile_mcp_get_knowledge_base_document | Read one current knowledge-base markdown document after listing its path | Read |
greptile_mcp_get_me | Identify the caller and discover the organizations available to other tools | Read |
greptile_mcp_get_merge_request | Get one pull request or merge request with metadata, statistics, comments, up to 10 recent | Read |
greptile_mcp_list_analytics_filter_options | List exact team names, repository names, or author logins available to the caller for analytics | Read |
greptile_mcp_list_analytics_findings | List review findings visible to the caller, newest first, with optional exact scope, severity | Read |
greptile_mcp_list_code_reviews | List code-review runs visible to the caller, newest first, optionally filtered by repository | Read |
greptile_mcp_list_custom_context | List saved review rules and learned patterns visible to the caller, newest first | Read |
greptile_mcp_list_knowledge_base_documents | List paths in one repository's current published knowledge base to map its documented | Read |
greptile_mcp_list_knowledge_bases | Discover repositories with reachable Greptile knowledge-base data; start here before asking how | Read |
greptile_mcp_list_merge_request_comments | List all matching comments for one pull request or merge request, newest first | Read |
greptile_mcp_list_merge_requests | List merge requests and pull requests visible to the caller, newest first | Read |
greptile_mcp_list_pull_requests | Alias of list_merge_requests with the same filters and result contract | Read |
greptile_mcp_list_repositories | List repositories visible to the caller in the selected organization, sorted by name | Read |
greptile_mcp_search_custom_context | Search visible custom-context bodies by case-insensitive substring, newest matches first | Read |
greptile_mcp_search_greptile_comments | Search Greptile-generated review comments by case-insensitive body substring across PR and | Read |
greptile_mcp_search_knowledge_base | Search one repository's current knowledge base for a case-insensitive substring when you know | Read |
greptile_mcp_create_custom_context | Create a persistent review rule or pattern in the selected organization | Read |
greptile_mcp_trigger_code_review | Request a new asynchronous Greptile review for an existing GitHub pull request or GitLab merge | Read |
