xkcdai
An MCP server that finds relevant xkcd comics during conversation by semantically matching the context to comic titles, alt text, and transcripts.
README
xkcdai
An MCP server that surfaces the right xkcd comic during a conversation, if one is relevant.
Live connector:
https://xkcdai.onrender.com/mcp— add it in claude.ai → Settings → Connectors. See Use the deployed MCP server.
It builds a semantic index over every xkcd comic (title + mouseover text +
transcript) using on-device embeddings, then exposes a single find_xkcd tool.
A Claude conversation can call it whenever the topic feels xkcd-shaped; a
relevance threshold means weak matches return nothing, so it stays quiet instead
of forcing a tenuous reference.
The fetched transcripts, explanations, and the embeddings are currently committed in this repo, under data/.
How it works
xkcd JSON API ─┐
├─► comics.json + explain.json ─► embeddings.npy ─► find_xkcd ─► Claude
explainxkcd ──┘ (cache) (bge-small) (cosine) (mentions it
(transcripts + if it fits)
explanations)
- Data: title + mouseover alt from the official API, plus the community transcript and explanation from explainxkcd.com. The explainxkcd context is essential: the official API dropped transcripts around comic ~1675, so without it the most-shared modern comics (e.g. #2347 Dependency) are unmatchable — their joke text lives only inside the image.
- Embeddings:
fastembed(ONNX) withBAAI/bge-small-en-v1.5— local, free, offline after first download, no PyTorch. Swap the model insrc/xkcdai/embed.py(e.g.BAAI/bge-base-en-v1.5for marginally better ranking at ~3× the size). - Search: a normalized numpy matrix + dot product. No vector DB needed for a few thousand comics.
- Restraint: because xkcd has a comic for almost everything, a similarity
cutoff alone can't judge relevance.
min_score(default0.62) is just a coarse floor; the real "should I bring this up?" decision is made by the calling model, guided by the score bands documented on thefind_xkcdtool.
Use the deployed MCP server (as custom connector)
The server is deployed at https://xkcdai.onrender.com on Render. Add it as a Claude custom connector to use it in the Claude web and mobile apps (note: the Free plan only allows one custom connector). Anyone can add the same URL in their own account.
In claude.ai (web — do this once; it then syncs to the mobile app):
- Settings → Connectors → Add custom connector.
- Paste the connector URL, including the
/mcppath:https://xkcdai.onrender.com/mcp - Leave OAuth blank (this server needs no auth) and click Add.
- The connector's
find_xkcdtool is now available in chats, on desktop and phone. For Claude to suggest comics on its own, also add the instruction from Make Claude suggest comics proactively to your Profile preferences.
Notes
- The server is public and unauthenticated — fine here (read-only comic search, no secrets). Don't reuse this pattern for anything sensitive without OAuth.
- A free Render instance sleeps when idle, so the first request after a nap is slow (cold start + model load), then snappy.
- Hosted from this repo via the Dockerfile and render.yaml;
pushes to
mainauto-redeploy.
Local setup
python -m venv .venv
# Windows (PowerShell): .venv\Scripts\Activate.ps1
# macOS/Linux: source .venv/bin/activate
pip install -e .
# 1. Fetch every comic's metadata.
xkcdai build
# 2. Fetch transcripts + explanations from explainxkcd (~2 min).
xkcdai enrich
# 3. Build the embedding index (downloads the model once; ~5-8 min to embed).
xkcdai build
Re-running later only fetches what's new.
Test it from the command line:
xkcdai search "my code finally compiled after an hour"
xkcdai search "arguing about the correct date format"
xkcdai search "spent more time automating it than doing it by hand"
Use locally as an MCP server
The server runs over stdio. Point your MCP host at it.
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"xkcdai": {
"command": "C:\\your\\path\\to\\xkcdai\\.venv\\Scripts\\xkcdai-server.exe",
"env": { "XKCDAI_DATA_DIR": "C:\\your\\path\\to\\xkcdai\\data" }
}
}
}
Claude Code (-s user makes it available in every project, not just this folder):
claude mcp add xkcdai -s user -e XKCDAI_DATA_DIR=C:\your\path\to\xkcdai\data -- C:\your\path\to\xkcdai\.venv\Scripts\xkcdai-server.exe
Always set XKCDAI_DATA_DIR, since the host launches the server from an arbitrary
working directory.
MCP only gives Claude the ability to call
find_xkcd— it won't volunteer comics on its own. See Make Claude suggest comics proactively.
Make Claude suggest comics proactively
Connecting the server only gives Claude the ability to call find_xkcd; it
won't reach for it unprompted. To make Claude volunteer comics, paste the
instruction below wherever that Claude reads persistent instructions:
- Claude Code — your global
~/.claude/CLAUDE.md(applies everywhere) or a per-repoCLAUDE.md; restart the session to load changes. - Claude.ai / Claude Desktop — Settings → Profile → "What personal preferences should Claude consider in responses?" (every plan, including free; syncs to the mobile app). Each person who uses the connector adds it in their own account.
When a conversation naturally lands on a topic xkcd is known for — programming,
science, math, statistics, engineering, the absurdity of standards, relationships,
everyday life — call the find_xkcd tool (xkcdai) with a short phrase describing the
topic. Then judge whether to bring it up:
- score >= 0.75 — strong match; mention it if it fits the moment
- 0.66-0.75 — only if it genuinely lands
- below that — stay silent
When you share one, give just that single comic: its number and title, its URL, and
quote the alt (mouseover) text — that's half the joke. At most one comic per topic,
and never force a tangential reference. When in doubt, say nothing.
It's still Claude's judgment, so it won't fire on every borderline topic — asking "is there an xkcd for this?" always triggers a lookup.
Configuration
XKCDAI_DATA_DIR— wherecomics.json,explain.json,embeddings.npy, andindex.jsonlive.find_xkcd(context, max_results=3, min_score=0.62)— lowermin_scorefor more (looser) suggestions, raise it to be stricter.
Maintenance
Pick up new comics periodically (both steps are incremental):
xkcdai enrich # new explainxkcd context
xkcdai build # fetch new comics + re-embed
Use xkcdai build --enrich to do both in one go, or --force on either command
to rebuild everything from scratch.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.