How to connect Greptile to OpenClaw
Connect Greptile to OpenClaw with ClawLink in one click — 21 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
GreptileOAUTH2MCPGreptile MCP lets authorized agents search connected codebases, inspect pull requests and code reviews, manage custom context, and analyze engineering knowledge bases.. Once connected, OpenClaw can read and act on Greptile from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Greptile access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Greptile setup: install one ClawHub skill, connect Greptile in the browser, and OpenClaw can call real Greptile actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Greptile skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Greptile" (hith3sh/greptile-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/greptile-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Greptile.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Greptile
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Greptile?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Greptile in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Greptile to mcp get analytics overview and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Greptile is connected in the dashboard, that agent calls the same 21 Greptile tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Greptile MCP for OpenClaw
Looking for a Greptile MCP server for OpenClaw? ClawLink connects Greptile to OpenClaw and exposes 21 Greptile tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Greptile integration works the same way.
What the OpenClaw Greptile integration can do
21 Greptile tools are ready for OpenClaw once the account is connected.
All 21 Greptile tools for OpenClaw
| Tool | What it does |
|---|---|
Mcp get analytics overview greptile_mcp_get_analytics_overview | Get review analytics for repositories visible to the caller, optionally intersected by exact |
Mcp get code review greptile_mcp_get_code_review | Get one code-review run by its stable id |
Mcp get custom context greptile_mcp_get_custom_context | Get one saved review rule or pattern and up to 10 linked review-comment references |
Mcp get knowledge base document greptile_mcp_get_knowledge_base_document | Read one current knowledge-base markdown document after listing its path |
Mcp get me greptile_mcp_get_me | Identify the caller and discover the organizations available to other tools |
Mcp get merge request greptile_mcp_get_merge_request | Get one pull request or merge request with metadata, statistics, comments, up to 10 recent |
Mcp list analytics filter options greptile_mcp_list_analytics_filter_options | List exact team names, repository names, or author logins available to the caller for analytics |
Mcp list analytics findings greptile_mcp_list_analytics_findings | List review findings visible to the caller, newest first, with optional exact scope, severity |
Mcp list code reviews greptile_mcp_list_code_reviews | List code-review runs visible to the caller, newest first, optionally filtered by repository |
Mcp list custom context greptile_mcp_list_custom_context | List saved review rules and learned patterns visible to the caller, newest first |
Mcp list knowledge base documents greptile_mcp_list_knowledge_base_documents | List paths in one repository's current published knowledge base to map its documented |
Mcp list knowledge bases greptile_mcp_list_knowledge_bases | Discover repositories with reachable Greptile knowledge-base data; start here before asking how |
Mcp list merge request comments greptile_mcp_list_merge_request_comments | List all matching comments for one pull request or merge request, newest first |
Mcp list merge requests greptile_mcp_list_merge_requests | List merge requests and pull requests visible to the caller, newest first |
Mcp list pull requests greptile_mcp_list_pull_requests | Alias of list_merge_requests with the same filters and result contract |
Mcp list repositories greptile_mcp_list_repositories | List repositories visible to the caller in the selected organization, sorted by name |
Mcp search custom context greptile_mcp_search_custom_context | Search visible custom-context bodies by case-insensitive substring, newest matches first |
Mcp search greptile comments greptile_mcp_search_greptile_comments | Search Greptile-generated review comments by case-insensitive body substring across PR and |
Mcp search knowledge base greptile_mcp_search_knowledge_base | Search one repository's current knowledge base for a case-insensitive substring when you know |
Mcp create custom context greptile_mcp_create_custom_context | Create a persistent review rule or pattern in the selected organization |
Mcp trigger code review greptile_mcp_trigger_code_review | Request a new asynchronous Greptile review for an existing GitHub pull request or GitLab merge |
Try it: find the Greptile tool you need
Browse the 21 Greptile tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Greptile to mcp get analytics overview and walk me through the result in plain English.
Use Greptile to mcp get code review and walk me through the result in plain English.
Use Greptile to mcp get custom context and walk me through the result in plain English.
Use Greptile to mcp get knowledge base document and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Greptile working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Greptile app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Greptile through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Greptile. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Greptile actions to the runtime in a format your agent can reliably use. | 21 tools for Greptile are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Greptile to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Greptile in the browser, and the 21 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Greptile skill but can't call the tools
The ClawHub skill teaches OpenClaw about Greptile, but the calls run through the ClawLink plugin and your connected account. Make sure Greptile is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Greptile from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Greptile tools
Greptile tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Greptile call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Greptile returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Greptile and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Greptile integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Greptile: link your Greptile account once in the browser and OpenClaw can call the Greptile API through 21 ready-made tools — no custom code or token handling.
How do I add Greptile to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Greptile skill from ClawHub, then you click Connect in the dashboard to authorize Greptile. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Greptile to OpenClaw?
About two minutes. Sign in, click Connect next to Greptile in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Greptile up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Greptile working from chat.
OpenClaw installed the Greptile skill but can't call the tools
The ClawHub skill teaches OpenClaw about Greptile, but the calls run through the ClawLink plugin and your connected account. Make sure Greptile is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Connect DataRobot
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.