How do I find my Bible API Key?

Sign up at the [**API.Bible developer portal**](https://scripture.api.bible/signup), create a new application, and you will find your API Key on the application details page. Copy and paste it below.

Are there different languages supported?

Yes. The API provides access to hundreds of Bible versions in dozens of languages, including English, Spanish, Portuguese, French, and many others.

Can the agent show verses from specific versions?

Yes. Most tools require a `bibleId`. Use the `list_bibles` tool to identify the correct ID for the version you wish to audit.

Bible API MCP Server for VS Code Copilot 6 tools — connect in under 2 minutes

Name: Bible API
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 6 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Bible API and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "bible-api": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Bible API MCP Server

Empower your AI agent to orchestrate your entire biblical research workflow with Bible API, the authoritative source for global scripture data. By connecting the American Bible Society's API to your agent, you transform complex verse lookups into a natural conversation. Your agent can instantly search for keywords across hundreds of Bible versions, audit chapter contents, and retrieve detailed verse metadata without you ever touching a technical portal. Whether you are conducting theological research or managing daily devotionals, your agent acts as a real-time biblical consultant, ensuring your data is always grounded in official, historically accurate translations.

GitHub Copilot Agent mode brings Bible API data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Scripture Auditing — Search for specific keywords or phrases across multiple Bible versions and retrieve cleaned text metadata.
Version Oversight — List and query hundreds of Bible translations across dozens of languages to maintain a clear view of linguistic nuances.
Verse Discovery — Retrieve specific verses or entire chapters using unique identifiers to assist in theological study.
Book Intelligence — List all books within a specific Bible version to understand the organizational structure of the canon.
Metadata Discovery — Retrieve detailed descriptions and abbreviations for Bible versions to identify the perfect source for your research.

The Bible API MCP Server exposes 6 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Bible API to VS Code Copilot via MCP

Follow these steps to integrate the Bible API MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Bible API

Ask Copilot: "Using Bible API, help me...". 6 tools available

Why Use VS Code Copilot with the Bible API MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Bible API through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Bible API + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Bible API MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Bible API MCP Tools for VS Code Copilot (6)

These 6 tools become available when you connect Bible API to VS Code Copilot via MCP:

get_bible_chapter

Get the content of a specific chapter

get_bible_details

Get metadata for a specific Bible ID

get_bible_verse

Get the text of a specific verse

list_bible_books

List all books in a specific Bible version

list_bibles

List all available Bible versions and languages

search_bible_text

Search for keywords or phrases across a Bible version

Example Prompts for Bible API in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Bible API immediately.

"Search for 'love' in the English Standard Version (bibleId: de4e12af7f895f10-01) using Bible API."

"Show the content of Genesis chapter 1 from the King James Version."

"List all Bible versions available in 'Portuguese'."

Troubleshooting Bible API MCP Server with VS Code Copilot

Common issues when connecting Bible API to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Bible API + VS Code Copilot FAQ

Common questions about integrating Bible API MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.