Bible Verse Skill

What this skill does

Give your agent scripture on demand. Call it as an MCP tool to fetch any book, chapter and verse across KJV, ASV and more — or a random verse. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Bible Verse Skill — exactly what your agent gets back when it makes the call.

vervekit · bibletool call

{
  "book": "Genesis",
  "chapter": 5,
  "verse": 17,
  "version": "KJV"
}

result

text: But with thee will I establish my covena…
book: Genesis
abbr: gn
chapter: 6
verses: [ 1 item ]
version: KJV
testament: Old Testament
bookNumber: 1

+3 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Turn IDs into detail

Enable Bible Verse and your app can add bible verse to your app — expand an identifier into full structured detail — in a single call, no integration per source.

A tool your agent reaches for

Over MCP, your model calls bible to enrich data mid-workflow exactly when it's needed.

Enrich from your backend

Call Bible Verse over REST to add bible verse to your app across a batch in a server-side job, one key for all of it.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

bible

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/bible

Ask your agent

“Enable Bible Verse and ask your agent to add bible verse to your app.”
“Use the Bible Verse skill for me.”

Bible Verse Skill, answered

How to connect it over MCP or REST.

How do I add Bible Verse to my app or agent?

Enable the Bible Verse Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the bible tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add bible verse to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Bible Verse appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Bible Verse call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Bible Verse is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Bible Verse is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Turn IDs into detail

A tool your agent reaches for

Enrich from your backend

Bible Verse Skill, answered

Give your software a way to act on the world.

Scaling in production?