OBS-TF MCP

The OBS Theological Formation tool server

A Model Context Protocol server that lets AI assistants fetch Open Bible Stories + Five Movements study content — structured tools, not a standalone translation app.

What is MCP?

A standard way for AI apps to call tools

Model Context Protocol (MCP) is how AI clients — Claude, Cursor, custom coaches, BT Servant, and others — connect to a remote server and invoke structured tools. The client sends a tool name and arguments; the server returns typed data the model can ground on.

Client

Any MCP-compatible assistant or app that can register a remote server URL.

Server

This Worker: exposes discovery and study-manual tools over /mcp.

Tools

Named operations with schemas — e.g. fetch_obs_study_manual — returning JSON or markdown.

This server

What OBS-TF MCP provides

Structured access to OBS Theological Formation manuals — paced observe → discuss → draft → check → serve → share sessions for Open Bible Stories (1–50).

Audience

Who this is for

Integrators and agent authors who need trustworthy OBS-TF content behind an MCP client — not end-user translation software.

Integrators & coaches

Wire https://obs-5m-mcp.unfoldingword.workers.dev/mcp into BT Servant–style coaches, Claude Desktop (mcp-remote), Cursor, or any Streamable HTTP MCP client. Call tools; present the returned questions and instructions.

Agent developers

Follow the recommended tool loop: discover language → pick story → load framework → pace with part=…. See the developer guide for the full contract.

Ecosystem

Sibling to Translation Helps MCP

Part of the BT Servant ecosystem by unfoldingWord. Two servers, complementary jobs:

Translation Helps MCP — tc-helps.mcp.servant.bible — scripture text, TN / TW / TA / TQ, passage tools, and classic OBS helps.

OBS-TF MCP — this server — OBS Theological Formation / Five Movements study manuals for translator and church formation sessions.

Connect

Endpoints

Point an MCP client at the server URL. Use the guide for tool contracts; chat and X-ray are optional demos.

Streamable HTTP MCP at /mcp. Same client setup as Translation Helps: Cursor uses a url; Claude Desktop uses mcp-remote. POST requires Accept: application/json, text/event-stream.

Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "obs-tf": {
      "url": "https://obs-5m-mcp.unfoldingword.workers.dev/mcp"
    }
  }
}
Claude Desktop / mcp-remote
{
  "mcpServers": {
    "obs-tf": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://obs-5m-mcp.unfoldingword.workers.dev/mcp"]
    }
  }
}
Direct HTTP (Streamable MCP)
POST https://obs-5m-mcp.unfoldingword.workers.dev/mcp
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"tools/list"}