How to connect Mintlify to Hermes Agent
Connect Mintlify to Hermes with ClawLink: paste your Mintlify key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
MintlifyAPI KEYMCPMintlify is a documentation platform.. Once connected, Hermes Agent can read and act on Mintlify from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Mintlify 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 Mintlify setup: pair once in the browser and your always-on Hermes agent can act on Mintlify 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 Mintlify.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Mintlify
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Mintlify?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Mintlify in the ClawLink dashboard — paste your Mintlify API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Mintlify, summarize it in plain English, and point out anything that needs attention.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Mintlify is connected in the dashboard, that agent calls the same 14 Mintlify tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Mintlify MCP for Hermes
Looking for a Mintlify MCP server for Hermes Agent? ClawLink connects Mintlify to Hermes Agent and exposes 14 Mintlify tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Mintlify integration works the same way.
What the Hermes Agent Mintlify integration can do
14 Mintlify tools are ready for Hermes Agent once the account is connected.
All 14 Mintlify tools for Hermes
| Tool | What it does |
|---|---|
Get agent job mintlify_get_agent_job | Retrieve the status and details (status, PR link, model, source repo/ref) of a docs agent job |
Get assistant caller stats mintlify_get_assistant_caller_stats | Get assistant query counts broken down by caller type (web, api, other, total) for a date range |
Get assistant conversations mintlify_get_assistant_conversations | Export the AI assistant conversation history (question, answer, cited sources, resolution |
Get feedback mintlify_get_feedback | Export a project's user feedback (thumbs / contextual comments / agent feedback), optionally |
Get feedback by page mintlify_get_feedback_by_page | Get feedback counts (thumbs up/down, code, total) aggregated per documentation page path for a |
Get page views mintlify_get_page_views | Export per-path and site-wide content view counts split by human vs AI traffic |
Get search queries mintlify_get_search_queries | Export documentation search terms ordered by hit count (with CTR and top clicked page) |
Get unique visitors mintlify_get_unique_visitors | Export per-path and site-wide approximate distinct visitor counts split by human vs AI traffic |
Get update status mintlify_get_update_status | Get the status and details (queued / in_progress / success / failure, logs, commit, screenshot) |
Create agent job mintlify_create_agent_job | Start a background documentation agent job from a natural-language prompt |
Send agent message mintlify_send_agent_message | Send a follow-up instruction to an existing, in-progress docs agent job (asynchronous) |
Trigger automation mintlify_trigger_automation | Trigger a custom-schedule automation (workflow) to run immediately |
Trigger preview mintlify_trigger_preview | Create or update a preview deployment of the docs project for a Git branch (redeploys if a |
Trigger update mintlify_trigger_update | Queue a production deployment of the docs project from its configured branch |
Try it: find the Mintlify tool you need
Browse the 14 Mintlify tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Mintlify, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mintlify, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mintlify, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mintlify, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key 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 Mintlify working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Mintlify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mintlify account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mintlify. | 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 Mintlify actions to the runtime in a format your agent can reliably use. | 14 tools for Mintlify are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Mintlify 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 Mintlify in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Mintlify key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Mintlify
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 Mintlify 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 Mintlify tools
Mintlify 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 Mintlify 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.
Mintlify 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.
API key setup works but results look incomplete
Double-check that the API key for Mintlify has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Mintlify integration?
Yes. ClawLink is the fastest way to connect Hermes to Mintlify: link your Mintlify account once in the browser and Hermes Agent can call the Mintlify API through 14 ready-made tools — no custom code or token handling.
How do I connect Mintlify 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 Mintlify in the dashboard and Hermes can use it from the next message — no config files, and the Mintlify key you paste is stored server-side instead of in your environment.
How long does it take to connect Mintlify to Hermes Agent?
About two minutes. Sign in, click Connect next to Mintlify in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Mintlify up myself?
The alternative to ClawLink is usually manual API key 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 Mintlify working from chat.
Hermes paired but still can't use Mintlify
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
Hermes GitHub integration
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.