# How to connect Greptile to Hermes Agent (no API keys) > Connect Greptile to Hermes with ClawLink in one click — 21 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/greptile Most guides for giving Hermes Agent Greptile access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Greptile setup: pair once in the browser and your always-on Hermes agent can act on Greptile for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Greptile. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Greptile** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect greptile # connect Greptile (browser OAuth) npx -y @useclawlink/cli actions greptile # list available actions npx -y @useclawlink/cli run greptile --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Greptile in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Greptile to mcp get analytics overview and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Greptile MCP for Hermes Looking for a Greptile MCP server for Hermes Agent? ClawLink connects Greptile to Hermes Agent and exposes 21 Greptile tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Greptile integration](https://claw-link.dev/openclaw/greptile) works the same way. ## What the Hermes Agent Greptile integration can do 21 Greptile tools are ready for Hermes Agent once the account is connected. ### All 21 Greptile tools for Hermes | 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 | ## Example prompts **Mcp Get Analytics Overview** > Use Greptile to mcp get analytics overview and walk me through the result in plain English. **Mcp Get Code Review** > Use Greptile to mcp get code review and walk me through the result in plain English. **Mcp Get Custom Context** > Use Greptile to mcp get custom context and walk me through the result in plain English. **Mcp Get Knowledge Base Document** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Greptile Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Greptile integration? Yes. ClawLink is the fastest way to connect Hermes to Greptile: link your Greptile account once in the browser and Hermes Agent can call the Greptile API through 21 ready-made tools — no custom code or token handling. ### How do I connect Greptile to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Greptile in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Greptile to Hermes Agent? About two minutes. Sign in, click Connect next to Greptile in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Greptile working from chat. ### Hermes paired but still can't use Greptile Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Connect DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Connect Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.