bskorea.or.kr から韓国語聖書にアクセスするための MCP (Model Context Protocol) サーバーです。
特徴:
⚡️ インメモリキャッシュ: 30分のTTLで、繰り返しリクエストを高速化
🔄 自動リトライ: 指数バックオフ（3回リトライ、1秒→2秒→4秒）による一時的な障害への対応
🛡️ 堅牢なエラーハンドリング: try/catch と適切なフォールバック
✅ 入力バリデーション: Zod スキーマを使用
🏥 ヘルスチェック: 監視用ツール
📚 全66巻: 5つの翻訳バージョンをサポート
🔍 全文検索: 聖書全巻を対象とした検索
Node.js 20以上 が必要です。
Related MCP server: biblebridge-mcp
この MCP サーバーは以下のツールを提供します：
韓国語聖書の章全体を取得
特定の節や節の範囲を取得
キーワードを含む節を検索
利用可能な全巻のリストを表示
異なる韓国語翻訳間での節の比較
npm を使用してグローバルにインストールします：
npm install -g bible-ko-mcpまたは npx で直接使用します（インストール不要）：
npx -y bible-ko-mcpget-chapter特定の章のすべての節を取得します。
パラメータ:
book (string, 必須): 英語、韓国語、または巻コードでの書名
例: "Genesis", "창세기", "gen"
chapter (number, 必須): 章番号
version (string, オプション): 聖書翻訳バージョン (デフォルト: "GAE")
オプション: "GAE", "GAE1", "NIR", "KOR", "CEV"
例:
{
"book": "Genesis",
"chapter": 1,
"version": "GAE"
}get-verses章から特定の節を取得します。
パラメータ:
book (string, 必須): 書名または巻コード
chapter (number, 必須): 章番号
verseStart (number, 必須): 開始節番号
verseEnd (number, オプション): 終了節番号 (デフォルトは verseStart)
version (string, オプション): 聖書翻訳バージョン (デフォルト: "GAE")
例:
{
"book": "John",
"chapter": 3,
"verseStart": 16,
"verseEnd": 17,
"version": "GAE"
}search-bible特定のキーワードを含む節を検索します。
パラメータ:
query (string, 必須): 韓国語または英語での検索クエリ
version (string, オプション): 聖書翻訳バージョン (デフォルト: "GAE")
注意: 検索は聖書全66巻を対象とし、フォールバック結果を含みます。
例:
{
"query": "사랑",
"version": "GAE"
}list-books聖書で利用可能な全巻をリストアップします。
パラメータ:
testament (string, オプション): 旧約・新約でのフィルタリング ("OT" または "NT")
例:
{
"testament": "NT"
}compare-translations異なる韓国語翻訳間で節を比較します。
パラメータ:
book (string, 必須): 書名または巻コード
chapter (number, 必須): 章番号
verse (number, 必須): 節番号
versions (array, オプション): 比較するバージョンコードの配列 (デフォルト: 全バージョン)
例:
{
"book": "John",
"chapter": 3,
"verse": 16,
"versions": ["GAE", "NIR", "KOR"]
}GAE: 改訂改訳 (Revised Korean Standard Version)
GAE1: 改訂ハングル (Korean Revised Version)
NIR: 新翻訳聖書 (New Korean Revised Version)
KOR: 共同翻訳 (Common Translation)
CEV: CEV (Contemporary English Version)
Genesis (창세기): gen
Exodus (출애굽기): exo
Leviticus (레위기): lev
Numbers (민수기): num
Deuteronomy (신명기): deu
... (詳細はソースコードのリストを参照)
Matthew (마태복음): mat
Mark (마가복음): mrk
Luke (누가복음): luk
John (요한복음): jhn
Acts (사도행전): act
... (詳細はソースコードのリストを参照)
Claude Desktop の設定に追加してください：
~/Library/Application Support/Claude/claude_desktop_config.json を編集：
{
"mcpServers": {
"bible-ko": {
"command": "npx",
"args": [
"-y",
"bible-ko-mcp"
]
}
}
}`%APPDATA%\Claude\claude_desktop_config.json
Compare a verse across different Korean translations
| Name | Required | Description | Default |
|---|---|---|---|
| book | Yes | Book name (English or Korean) or code (e.g., 'Genesis', '창세기', 'gen') | |
| verse | Yes | Verse number | |
| chapter | Yes | Chapter number | |
| versions | No | Array of version codes to compare (default: all versions) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states the basic function without disclosing any behavioral traits (e.g., read-only, no side effects, auth requirements). The description is too brief for a tool with no annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded, and no wasted words. However, it is slightly under-specified given lack of annotations; could include more useful context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should explain what the tool returns (e.g., comparison format, translations listed). It only says 'compare', leaving the agent to guess the return structure and behavior. Incomplete for a tool with 4 parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the input schema already documents all parameters. The description adds no additional meaning beyond 'compare verse across translations'. Baseline 3 is appropriate as schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Compare a verse across different Korean translations', which is specific about the verb (compare), resource (verse), and scope (Korean translations). It effectively distinguishes from sibling tools like 'get-chapter' or 'get-verses'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (when you need to compare translations of a specific verse) but does not explicitly state when not to use it or mention alternatives. The sibling tool names provide context, but no direct guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get all verses from a specific chapter of the Korean Bible
| Name | Required | Description | Default |
|---|---|---|---|
| book | Yes | Book name (English or Korean) or code (e.g., 'Genesis', '창세기', 'gen') | |
| chapter | Yes | Chapter number | |
| version | No | Bible translation version (default: GAE) | GAE |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic retrieval action, omitting details about read-only nature, output format, or any constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no unnecessary words or repetition. It is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core functionality but lacks context about output format, edge cases, or integration with sibling tools. Given the tool's simplicity, it is mostly complete but could be improved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema, simply restating the purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'all verses from a specific chapter of the Korean Bible', distinguishing it from sibling tools like get-verses (probably individual verses) and search-bible.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide explicit guidance on when to use this tool versus alternatives like get-verses or compare-translations. Usage context is implied but not articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get specific verse(s) from a chapter
| Name | Required | Description | Default |
|---|---|---|---|
| book | Yes | Book name (English or Korean) or code (e.g., 'Genesis', '창세기', 'gen') | |
| chapter | Yes | Chapter number | |
| version | No | Bible translation version (default: GAE) | GAE |
| verseEnd | No | Ending verse number (optional, defaults to verseStart) | |
| verseStart | Yes | Starting verse number |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full responsibility for behavioral disclosure. It fails to mention any behavioral aspects such as read-only nature, error handling, or what happens if verses are missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, brief sentence that gets straight to the point. It is concise, but could benefit from a bit more context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's core purpose but lacks detail on output format, authentication needs, rate limits, or usage scenarios. Given the moderate complexity (5 parameters, 1 enum), more context would help the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, meaning the input schema already details each parameter well. The description adds no additional meaning beyond 'specific verse(s)', which is accurate but not enhancing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('specific verse(s) from a chapter'), making the tool's purpose immediately clear. It distinguishes from sibling 'get-chapter' which retrieves an entire chapter, and 'search-bible' which is for searching.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'get-chapter' for whole chapters or 'search-bible' for searches. The context is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Check the health status of the Bible Korean MCP server and API connectivity
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. It mentions checking health and connectivity but does not describe output format or whether authentication is needed. For a simple tool, this is acceptable but lacks detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with the action. No extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple health check tool with no parameters and no output schema, the description is sufficiently complete. It conveys purpose and scope, though it omits output details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; schema coverage is 100%. The description adds no parameter info, which is not needed. Baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks health status and API connectivity, a specific verb+resource. It is easily distinguished from siblings which perform Bible data operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly, the tool is for verifying server health before other operations, but no explicit when-to-use or exclusions are provided. For a simple health check, this is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all available books in the Bible
| Name | Required | Description | Default |
|---|---|---|---|
| testament | No | Filter by testament (OT/NT, optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility. It does not disclose read-only nature or any side effects, but it is safe for a list operation. Minimal disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, but it is minimally informative. Consider adding context about the return format.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list with one optional parameter, the description is adequate but does not explain return values or behavior when no filter is applied. Slightly incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter, but the description adds no additional information beyond what the schema provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'list' and the resource 'all available books in the Bible', distinguishing it from sibling tools like get-chapter or search-bible.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for listing books but lacks explicit guidance on when to use this tool versus alternatives, such as search-bible or get-verses.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search for verses containing specific keywords. Searches the first 10 chapters of each book — not a full-Bible search.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query (Korean or English) | |
| version | No | Bible translation version (default: GAE) | GAE |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description provides the key behavioral limitation (not full-Bible search). It adds value beyond schema by disclosing the restricted scope, but does not address other traits like read-only nature or authentication needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences, each adding distinct value: first states core action, second clarifies critical scope limitation. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's purpose and limitation but lacks any mention of output format or return value. Since there is no output schema, this gap reduces completeness for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes both parameters (query and version) with descriptions and enums. The description adds no additional semantic information about parameters beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Search') and resource ('verses containing specific keywords') and clearly distinguishes the tool by stating the limitation (first 10 chapters only), separating it from siblings like get-chapter or get-verses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states the scope (first 10 chapters) and implies this is for quick keyword searches, not a full-Bible search. However, it does not explicitly mention when to use alternatives like get-verses or compare-translations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.2.0compare-translations3 fields changedInput schema / properties / book / descriptionPrevious value: -"Book name (English or Korean) or code"New value: +"Book name (English or Korean) or code (e.g., 'Genesis', '창세기', 'gen')"Input schema / properties / chapter / minimumAdded value: +1Input schema / properties / verse / minimumAdded value: +1get-chapter1 field changedInput schema / properties / chapter / minimumAdded value: +1get-verses4 fields changedInput schema / properties / book / descriptionPrevious value: -"Book name (English or Korean) or code"New value: +"Book name (English or Korean) or code (e.g., 'Genesis', '창세기', 'gen')"Input schema / properties / chapter / minimumAdded value: +1Input schema / properties / verseEnd / minimumAdded value: +1Input schema / properties / verseStart / minimumAdded value: +1health-checkcompare-translationsget-chapterget-verseslist-bookssearch-bibleScored across 6 tools
Each tool has a clearly distinct purpose: compare-translations for cross-translation comparison, get-chapter for full chapters, get-verses for specific verses, health-check for server status, list-books for book listing, and search-bible for keyword search. No overlap.
Tool names follow a consistent pattern of lowercase hyphenated verb-noun (compare-translations, get-chapter, get-verses, list-books, search-bible), though health-check is a noun-noun compound, deviating slightly but still readable.
With 6 tools, the server is well-scoped for its domain, covering reading, searching, and comparison without being overly numerous or too sparse.
Core operations are covered (list books, get chapter/verses, search, compare), but notable gaps exist: no tool to list available translations, and the search is limited to the first 10 chapters of each book, which may hinder full-text discovery.
Bible translations, books, chapters, verses, and search
Read-only BSB and WEB Scripture evidence with provenance, context, comparison, and search.
Scripture-cited answers to any Bible question, plus verse text and study pages, for AI agents.
Bible corpus MCP server: scripture, Greek/Hebrew interlinear data, cross-refs, semantic search.
