How to connect API.Bible to Hermes Agent
Connect API.Bible to Hermes with ClawLink: paste your API.Bible key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine.
API.BibleAPI KEYMCPAPI.Bible allows developers to integrate Scripture content into their applications or websites for non-commercial purposes.. Once connected, Hermes Agent can read and act on API.Bible from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent API.Bible 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 API.Bible setup: pair once in the browser and your always-on Hermes agent can act on API.Bible 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 API.Bible.
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 API.Bible
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with API.Bible?"
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 API.Bible in the ClawLink dashboard — paste your API.Bible API key once.
Verify the connection by asking Hermes:
Pull the relevant data from API.Bible, 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 API.Bible is connected in the dashboard, that agent calls the same 19 API.Bible tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
API.Bible MCP for Hermes
Looking for a API.Bible MCP server for Hermes Agent? ClawLink connects API.Bible to Hermes Agent and exposes 19 API.Bible tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw API.Bible integration works the same way.
What the Hermes Agent API.Bible integration can do
19 API.Bible tools are ready for Hermes Agent once the account is connected.
All 19 API.Bible tools for Hermes
| Tool | What it does |
|---|---|
Get all books api_bible_get_all_books | Retrieve all books for a specific Bible version |
Get audio bible api_bible_get_audio_bible | Retrieve details of a specific audio Bible by its ID |
Get audio book api_bible_get_audio_book | Retrieve a single audio Book object for a given audio Bible ID and book ID |
Get audio chapter api_bible_get_audio_chapter | Retrieve a single audio chapter with mp3 resource URL |
Get bible api_bible_get_bible | Retrieve details of a specific Bible version by its ID |
Get book api_bible_get_book | Retrieve a single Book object for a given Bible version and book ID |
Get chapter api_bible_get_chapter | Retrieve a complete chapter with all verses from a Bible version |
Get passage api_bible_get_passage | Retrieve a Bible passage by ID |
Get section api_bible_get_section | Retrieve detailed content for a Bible section by ID |
Get sections api_bible_get_sections | Retrieve a list of sections for a specific book in a Bible version |
Get supported versions api_bible_get_supported_versions | Retrieve a list of available Bible versions (translations) from API.Bible |
Get verse api_bible_get_verse | Retrieve a specific Bible verse by ID |
List audio bibles api_bible_list_audio_bibles | Retrieve an array of audio Bible objects authorized for the current API Key |
List audio books api_bible_list_audio_books | Retrieve all books for a specific audio Bible version |
List audio chapters api_bible_list_audio_chapters | Retrieve a list of audio chapters for a specific book in an audio Bible version |
List chapter sections api_bible_list_chapter_sections | Retrieve an array of section objects for a specific chapter in a Bible version |
List chapters api_bible_list_chapters | Retrieve an array of Chapter objects for a given Bible version and book |
List verses api_bible_list_verses | Retrieve an array of verses for a specific chapter in a Bible version |
Search verses api_bible_search_verses | Search for Bible verses containing specified keywords or passage references |
Try it: find the API.Bible tool you need
Browse the 19 API.Bible 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 API.Bible, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from API.Bible, 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 API.Bible working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the API.Bible API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected API.Bible 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 API.Bible. | 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 API.Bible actions to the runtime in a format your agent can reliably use. | 19 tools for API.Bible are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes API.Bible 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 API.Bible in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the API.Bible 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 API.Bible
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 API.Bible 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 API.Bible tools
API.Bible 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 API.Bible 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.
API.Bible 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 API.Bible 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 API.Bible integration?
Yes. ClawLink is the fastest way to connect Hermes to API.Bible: link your API.Bible account once in the browser and Hermes Agent can call the API.Bible API through 19 ready-made tools — no custom code or token handling.
How do I connect API.Bible 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 API.Bible in the dashboard and Hermes can use it from the next message — no config files, and the API.Bible key you paste is stored server-side instead of in your environment.
How long does it take to connect API.Bible to Hermes Agent?
About two minutes. Sign in, click Connect next to API.Bible in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring API.Bible 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 API.Bible working from chat.
Hermes paired but still can't use API.Bible
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
GitHub tools
Manage repositories, issues, pull requests, and workflows
Hermes PagerDuty integration
Manage incidents, on-call schedules, and services
Hermes SafetyCulture integration
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.