mcpField
F
Feason Context

Feason Context

Remote
feason.comMemory & Knowledge0Updated 8w ago

About Feason Context

Feason Context provides typed TypeScript and Python clients for a REST API returning source-grounded Christian research evidence. It is for applications that need exact passages, provenance, citations, and named tradition coverage; the hosted MCP service is documented separately.

Key features

  1. 01Typed TypeScript client
  2. 02Typed Python client
  3. 03OpenAPI 3.1 contract
  4. 04Evidence packets with provenance
  5. 05Stable citations and tradition coverage

Use cases

  1. 01Retrieve passages for Christian research questions
  2. 02Integrate source evidence into an application

MCP support

The hosted Feason Context service is available as a remote MCP server; the included SDKs access its REST API and do not include the server implementation.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://www.feason.com/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Feason Context SDKs

Typed, dependency-free TypeScript and Python clients for the Feason Context REST API, plus its OpenAPI 3.1 contract.

Feason Context supplies source-grounded Christian research material with exact passages, provenance, stable citations, named tradition coverage, and explicit coverage boundaries. Applications decide how to use the returned evidence.

Included

  • typescript/ — @feason/context
  • python/ — feason-context
  • openapi/feason-context-openapi.yaml — the public REST contract
  • contract.json — versioned endpoint metadata used to generate both clients
  • server.json — official MCP Registry metadata for the hosted remote server
  • DIRECTORY_LISTING.md — reusable, boundary-aware MCP directory copy

The hosted service remains at https://www.feason.com. These clients do not contain the Feason corpus, production credentials, user data, retrieval engine, or server implementation. Tokens are accepted at runtime and are never persisted.

TypeScript

import { FeasonContextClient } from "@feason/context";

const client = new FeasonContextClient({ token: process.env.FEASON_CONTEXT_TOKEN! });
const packet = await client.evidencePacket({ question: "How did early Christians describe grace?" });
console.log(packet);

Python

import os
from feason_context import FeasonContextClient

client = FeasonContextClient(os.environ["FEASON_CONTEXT_TOKEN"])
packet = client.evidence_packet("How did early Christians describe grace?")
print(packet)

Development

node scripts/generate-clients.mjs --check
npm --prefix typescript install
npm --prefix typescript run build
npm --prefix typescript test
python3 -m unittest discover -s python -p 'test_*.py'

Distribution

The SDK package names are reserved in their manifests but are not advertised as publicly installable until their registry records are verified. See PUBLISHING.md for the release preflight and verification sequence.

The hosted MCP service is described separately by server.json. Directory descriptions should preserve Feason's evidence-layer boundaries; see DIRECTORY_LISTING.md.

Security

Do not place API tokens in source, examples, issues, or test fixtures. See SECURITY.md for private vulnerability reporting.

License

MIT. See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.