Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/davidbuenov/dbv-mcp-server/llms.txt

Use this file to discover all available pages before exploring further.

The dbv-unreal-python-api skill exposes its search capability through three independent access paths: MCP tools (for Claude Desktop and compatible clients), a CLI interface (for Claude Code and direct shell use), and HTTP REST endpoints (for the Unreal MCP Web Client). All three paths query the same local knowledge base and return the same ranked results.
Two-step workflow: call dbv_unreal_dev_guide first to understand the conceptual approach for a subsystem, then use dbv_python_unreal_api with the exact:ClassName syntax to retrieve the precise class and method signatures before writing any code.

​
MCP Tools (Claude Desktop / claude.ai)

mcp_server.py exposes four tools over the MCP stdio transport. Claude calls them automatically when the server is registered in claude_desktop_config.json.

​
dbv_python_unreal_api(query: str)

Natural language query for class and method syntax. Returns the full Markdown content of the most relevant class pages from the local knowledge base. Supports exact:ClassName syntax to bypass semantic scoring and jump directly to a known class name.

​
dbv_python_unreal_api_status()

Returns the knowledge base version and the total number of indexed classes.

​
dbv_unreal_dev_guide(query: str)

Natural language query for workflow and conceptual guides. Returns chunked Markdown content from the most relevant guide pages.

​
dbv_unreal_dev_guide_status()

Returns the guides knowledge base version, total guide count, and total chunk count.

​
Example Queries

dbv_python_unreal_api("spawn actor at position")
dbv_python_unreal_api("exact:MaterialEditingLibrary")
dbv_python_unreal_api("exact:EditorAssetLibrary")
dbv_python_unreal_api("list all assets in a folder")

dbv_unreal_dev_guide("connect texture in material instance")
dbv_unreal_dev_guide("how to create PCG spawner")
dbv_unreal_dev_guide("logical flow to hot-compile a Blueprint")
dbv_unreal_dev_guide("how to structure a Niagara particle system")

​
CLI Commands (Claude Code / direct use)

All commands are relative to the repository root. This is how Claude Code invokes the skill via Bash/code execution — no server or open port required. 
# Search the Python API reference
python skills/dbv-unreal-python-api/scripts/search_engine.py search "spawn actor at position"
python skills/dbv-unreal-python-api/scripts/search_engine.py search "exact:StaticMeshActor"
python skills/dbv-unreal-python-api/scripts/search_engine.py search "exact:MaterialEditingLibrary"

# Search conceptual dev guides
python skills/dbv-unreal-python-api/scripts/search_engine.py search-guides "connect texture material instance"
python skills/dbv-unreal-python-api/scripts/search_engine.py search-guides "how to create PCG spawner"

# Check knowledge base status
python skills/dbv-unreal-python-api/scripts/search_engine.py status
python skills/dbv-unreal-python-api/scripts/search_engine.py guides-status
Optional flag for all search and search-guides commands: 
--max-results N   # Return up to N classes or guides (default: 3)

​
REST Endpoints (Web Client)

When the Unreal MCP Web Client is running on port 5000, server.py imports search_engine.py directly and exposes these HTTP endpoints: 
GET http://localhost:5000/api/docs/search?q=MaterialEditingLibrary
GET http://localhost:5000/api/docs/status
GET http://localhost:5000/api/guides/search?q=connect+texture+material
GET http://localhost:5000/api/guides/status
All responses are plain text Markdown (for search) or JSON (for status), suitable for direct display or further processing.

​
Scoring System

The search engine uses keyword tokenization to rank results. Tokens are extracted from the query using the pattern [a-zA-Z_][a-zA-Z0-9_]{2,}.

​
Python API scoring (per token, per class)

Match typeScore
Exact match on class name+10.0
Class name contains token (or vice versa)+4.0
Exact match on an index keyword+3.0
Partial match on an index keyword+1.5
Token found in category name+0.5

​
exact:ClassName syntax

Prefixing the query with exact: bypasses the scoring algorithm entirely. The engine performs a case-insensitive lookup directly against the class name index and returns that single class’s full documentation page. Use this whenever you already know the class name you need: 
exact:MaterialEditingLibrary
exact:PCGGraphInterface
exact:ScopedEditorTransaction

​
Dev guides scoring (per token, per guide)

Match typeScore
Token found in guide title+5.0
Token exactly matches the guide category+3.0
Exact match on a guide keyword+2.0
Partial match on a guide keyword+1.0
Results for both search modes are capped at 12,000 characters total context to avoid saturating the AI’s context window, with individual class pages capped at 6,000 characters each.

Build docs developers (and LLMs) love

Get started for freeTalk to us