English Français العربية

world.wheelofheaven.mcp/corpus

Registre officiel Données et bases de données

Read-only Wheel of Heaven corpus: myth search, primary texts, datasets, typed graph. CC0.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http corpus 'https://mcp.wheelofheaven.world/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "corpus": {
            "type": "http",
            "url": "https://mcp.wheelofheaven.world/mcp"
        }
    }
}
NPM package @wheelofheaven/mcp
Claude Code 
claude mcp add corpus -- npx -y @wheelofheaven/mcp@0.1.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "corpus": {
            "command": "npx",
            "args": [
                "-y",
                "@wheelofheaven/mcp@0.1.0"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. mcp.wheelofheaven.world
  2. Endpoints
  3. Install
  4. Tools
  5. Development
  6. Architecture
  7. Related repositories
  8. License

mcp.wheelofheaven.world

Read-only MCP server for the Wheel of Heaven corpus. It wraps the static JSON API at api.wheelofheaven.world so AI agents can search and retrieve the corpus with full epistemic metadata (claim types, editorial passes, citations).

Design rationale and tool-surface spec: .claude/plans/strategy-mcp-server.md in the org .claude repo.

Endpoints

  • /mcp — Streamable HTTP (canonical)
  • /sse — legacy SSE transport
  • / — server info (JSON)

Install

Remote (recommended — nothing to run locally):

claude mcp add --transport http wheel-of-heaven https://mcp.wheelofheaven.world/mcp

Local stdio via npm (@wheelofheaven/mcp):

npx -y @wheelofheaven/mcp

Registry listing: world.wheelofheaven.mcp/corpus in the official MCP registry.

Tools

Fact layer — source-grounded data, no interpretation applied:

ToolPurpose
search_corpusFuzzy full-text search over wiki, timeline, library books, articles, and news (~290 documents; token-AND with OR fallback)
get_entryOne wiki/timeline/articles/news entry as markdown with claim_type, editorial_pass, typed related-content edges, and canonical citation URLs; 9-language support via lang
get_passageA chapter of a digitized primary source text as numbered paragraphs with stable reference IDs (e.g. GEN-1:26); ref filters to one verse
get_sourceBibliography lookup by stable ID or search — every record carries the source-program classification (family, stance, relation), critical sources included
compare_traditionsRows from the comparative datasets: flood-myths, divine-council-index, theomachy-crossrefs, world-ages, prophets-and-religions
query_graphTyped 1-hop ego network of any corpus node (see_also, in_body, cites_source, same_tradition, same_age, comparison_of)

Interpretation layer — explicitly the project's own reading, labeled as such:

ToolPurpose
get_interpretationThe Wheel of Heaven framework's reading of a topic (curated context documents, or the closest wiki entry), always carrying an interpretation-layer notice
get_methodThe editorial methodology: claim-type taxonomy, six-source rule, editorial passes — how to weigh everything else

Meta:

ToolPurpose
get_glossary_termCore terminology with renderings in all 9 site languages (exact-id match first)

Resources: the six /v1/context/* narrative documents (woh://context/{overview,hypothesis,terminology,timeline,sources,method}) plus woh://llms.txt.

Development

npm install
npm run dev        # wrangler dev on :8787
npm run typecheck
npm run deploy     # wrangler deploy (needs Cloudflare auth)

The server is stateless over the upstream API: every tool call fetches api.wheelofheaven.world/v1/…, with the ~600 KB search corpus cached in-memory per isolate for one hour (matching the API's edge-cache TTL).

Architecture

  • Cloudflare Workers + agents SDK (McpAgent Durable Object)
  • src/server.ts — transport-agnostic tool registration (reused by the future npm stdio build)
  • src/api.ts — /v1/ client + search-corpus cache
  • src/html.ts — deterministic body_html → markdown conversion

License

CC0-1.0 — like the corpus itself.

Questions fréquentes

Qu'est-ce que world.wheelofheaven.mcp/corpus ?

Read-only Wheel of Heaven corpus: myth search, primary texts, datasets, typed graph. CC0.

Comment installer world.wheelofheaven.mcp/corpus ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http corpus 'https://mcp.wheelofheaven.world/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour world.wheelofheaven.mcp/corpus ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

world.wheelofheaven.mcp/corpus est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient world.wheelofheaven.mcp/corpus ?

Il est publié par wheelofheaven. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.