Skip to content

MCP Server

The JickleJime MCP (Model Context Protocol) server lets AI tools search your Shadowdark knowledge base directly. Connect it to GitHub Copilot, Claude Desktop, or any MCP-compatible client to give your AI assistant access to rules, sessions, and campaign content.

What is MCP?

The Model Context Protocol is an open standard for connecting AI models to external data sources and tools. Instead of copy-pasting context into a chat window, MCP lets the AI call tools to search your knowledge base on demand.

Available tools

The MCP server exposes five tools:

Tool Purpose
search Hybrid search over the indexed corpus
ask Ask a question with a RAG-generated answer and citations
list_documents List all ingested documents with metadata
list_sources Discover available sources for filtering
read_document Read the full text of a specific document

Transport modes

The server supports two transport modes:

Stdio (local development)

The AI client launches the server as a subprocess and communicates over stdin/stdout. This is the recommended mode for local development — no network configuration needed.

dotnet run --project src/JickleJime.Mcp -- --stdio

HTTP Streamable (deployed environments)

The server runs as a web service and accepts MCP requests over HTTP at the /mcp endpoint. Use this for deployed environments where the server runs remotely.

dotnet run --project src/JickleJime.Mcp

Locally, ASP.NET Core uses its default ports (typically 5000/5001). In the container image, the server listens on port 8080 via ASPNETCORE_URLS. When an API key is configured, all requests require an Authorization: Bearer <key> header.

Getting started