Developer Portal

xHalo Unified MCP & Agent Service

Access structured scripture and Buddhist canon datasets, dynamic query APIs, and AI novel voice generation engines.

XHALO-MCPProductionRead-only

MCP & Agent Access

A single MCP Edge Worker owns protocol, OAuth, manifest, scope, and quota enforcement. Domain APIs retain REST ownership and do not expose separate MCP servers.

Production: Active

https://mcp.xhalo.co/mcp

Active Manifest

2026-07-31-search-tools

Protocol

2026-07-28

Transport

Stateless Streamable HTTP

Auth

OAuth 2.1 Authorization Code + PKCE S256

Endpoint

https://mcp.xhalo.co/mcp

Candidate manifest (disabled)

news.search · community.search · chat.rooms.list · email.send

MCP disabled; REST boundary retained

crawl.fetch · crawl.render · crawl.extract

bible.searchProductionside effects: none

mcp:tools:list · mcp:tools:call · bible:search

buddhist.searchProductionside effects: none

mcp:tools:list · mcp:tools:call · buddhist:search

REST API keys and MCP OAuth tokens are distinct credentials. API keys cannot sign in to MCP, and MCP tokens are never forwarded to domain APIs. The production endpoint requires OAuth 2.1 Authorization Code + PKCE and publishes only the reviewed Bible/Buddhist read-only tools.

CLOUDFLARE MCP PORTALNeeds verificationNo traffic

Internal MCP Portal

agents.xhalo.co is a candidate administrator entry point. It will not be published or receive traffic until DNS, the exact-email Access policy, and upstream OAuth synchronization pass live acceptance; use the direct MCP endpoint meanwhile.

https://agents.xhalo.co

callback: /servers-callback

Code Mode

Off

User auth

Required

Initial tools

bible.search, buddhist.search

New tools

Disabled by default

Portal-native portal_* session tools are not xHalo business tools. The Access service token is only for background synchronization and cannot replace a user's xHalo OAuth grant; REST API keys cannot sign in to the Portal.

APIs & Services

bible-data

XHALO-BIBLE-DATA

Structured raw scripture compiler & CDN datasets

Method:GET

Authentication:Authorization: Bearer <XHALO_API_KEY>

Endpoint

CDNhttps://bibledb.xhalo.co/api/scripture/chapter?lang={lang}&version={version}&book_slug={book_slug}&chapter={chapter}

Parameters & Schema

Parameter	Type	Required	Description
lang	string (Query)	Yes	Language code identifier, e.g. 'en' (English), 'zh-hans' (Simplified Chinese).
version	string (Query)	Yes	Bible translation code, e.g. 'KJV' (King James Version), 'ChiUns' (Chinese Union Version).
book_slug	string (Query)	Yes	Lowcase book identifier name, e.g. 'genesis', 'john'.
chapter	integer (Query)	Yes	Chapter number index (starting from 1).

JSON Response Sample

json

1{
2  "ok": true,
3  "chapter": {
4    "lang": "en",
5    "version": "KJV",
6    "book": 1,
7    "book_slug": "genesis",
8    "chapter": 1,
9    "verse_count": 31,
10    "data_key": "data/v1/books/en/KJV/genesis.json"
11  },
12  "payload": {
13    "lang": "en",
14    "version": "KJV",
15    "book": 1,
16    "book_slug": "genesis",
17    "book_name": "Genesis",
18    "chapter": 1,
19    "verses": [
20      { "verse": 1, "verse_id": "1-1-1", "ref": "en-KJV-1-1-1", "text": "In the beginning God created..." }
21    ]
22  }
23}