Urantia Papers MCP server

What it does

An MCP server providing access to The Urantia Papers—197 religious/philosophical texts comprising 14,500+ paragraphs and 4,400+ entities. It offers full-text search, semantic search, structured navigation, audio URLs, and entity cross-referencing for developers and AI agents studying or referencing the Papers.

• Search The Urantia Papers by keyword or semantic meaning to find passages relevant to a specific topic or question.
• Retrieve a specific paragraph with surrounding context and audio, or browse the table of contents to navigate papers and sections.
• Look up entities (beings, places, concepts) mentioned in the Papers and find all paragraphs that reference them.

Tools this server exposes

Tool	Does
search_urantia	Full-text search across all 14,500+ paragraphs with and/or/phrase modes and optional filtering by paper or part.
get_paragraph	Retrieve a single paragraph by reference ID in any of three formats, with optional surrounding context.
get_paper	Retrieve a complete paper with all its paragraphs and sections.
get_toc	Retrieve the table of contents showing the hierarchical structure of all 197 papers organized by parts.
list_papers	List all 197 papers with their metadata.
random_paragraph	Return a random paragraph from the Papers.
get_entity	Retrieve details about a named entity (being, place, concept, etc.) in the Papers.
list_entities	List all 4,400+ entities indexed in the Papers.
entity_paragraphs	Find all paragraphs that mention a specific entity.
get_audio	Retrieve audio URLs and metadata for a paragraph in available models and voices.
semantic_search	Search paragraphs using vector embeddings for semantic similarity.
generate_citation	Generate a citation for a paragraph in APA, MLA, Chicago, or BibTeX format.
get_embeddings	Get vector embeddings for paragraphs for custom semantic operations.
bible_lookup	Look up Bible passages (WEB translation) for cross-reference with Urantia Papers.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.