Valksor dictionary MCP servers
Free, read-only MCP servers (with JSON API mirrors) that ground LLMs in real dictionaries — attested lemmas, inflections and etymologies instead of invented words. Eight languages so far, all available through this hub's single passthrough endpoint — or individually if you only want one dictionary. No auth: connect once and the model sees each dictionary's tools under a language prefix.
1 hub endpoint 8 servers MCP JSON API free no auth
The servers
Grounds LLMs in the real Livonian dictionary at livonian.tech: attested words, full inflection tables, romanization.
https://livonian.valksor.com/mcp
Grounds LLMs in real Latin: Wiktionary lemmas, Morpheus-resolved inflections, citations.
https://latin.valksor.com/mcp
Grounds LLMs in real Church Slavonic: Old Church Slavonic lemmas, dual-number paradigms, transliteration.
https://slavonic.valksor.com/mcp
Grounds LLMs in real Scythian: reconstructed Proto-Scythian lemmas, etymologies, descendant trees to Ossetian and Khotanese.
https://scythian.valksor.com/mcp
Grounds LLMs in real Old Norse: Wiktionary lemmas and full inflection paradigms — definite forms, adjective families, the mediopassive.
https://norse.valksor.com/mcp
Grounds LLMs in real Latgalian: Wiktionary lemmas, inflection tables, diacritic romanization.
https://latgalian.valksor.com/mcp
Grounds LLMs in real Old English (Anglo-Saxon): Wiktionary lemmas, strong/weak paradigms, dual pronouns, English→Old English lookup.
https://anglo.valksor.com/mcp
Grounds LLMs in real Interslavic (Medžuslovjansky): a multilingual translation matrix, generated declensions and conjugations, English→Interslavic lookup.
https://interslavic.valksor.com/mcp
Connect once through the hub
The hub is the recommended MCP setup for general use. Add one remote
streamable-HTTP endpoint and it exposes every
dictionary's tools and prompts under the same names they use directly,
each prefixed by language: latin_search,
scythian_get_descendants, and each call is forwarded to the
owning server.
Claude Code — CLI
claude mcp add --transport http valksor https://mcp.valksor.com/mcp
Cursor · Cline
— remote url (~/.cursor/mcp.json)
{
"mcpServers": {
"valksor": { "url": "https://mcp.valksor.com/mcp" }
}
}
VS Code — .vscode/mcp.json
{
"servers": {
"valksor": { "type": "http", "url": "https://mcp.valksor.com/mcp" }
}
}
Rule of thumb: clients with native streamable-HTTP/SSE support take the
url directly (Claude Code, Cursor, Cline, VS Code);
stdio-only desktop apps wrap it with
npx -y mcp-remote <url>. For this hub, the URL is
https://mcp.valksor.com/mcp.
The hub mirrors the same passthrough over JSON:
https://mcp.valksor.com/api/<lang>/search (also
/inflections, or /descendants for scythian),
documented at /api/docs.
Connect a single dictionary instead
Use a dictionary's own endpoint when you want only one language exposed to the client:
claude mcp add --transport http livonian https://livonian.valksor.com/mcp claude mcp add --transport http latin https://latin.valksor.com/mcp claude mcp add --transport http slavonic https://slavonic.valksor.com/mcp claude mcp add --transport http scythian https://scythian.valksor.com/mcp claude mcp add --transport http norse https://norse.valksor.com/mcp claude mcp add --transport http latgalian https://latgalian.valksor.com/mcp claude mcp add --transport http anglo https://anglo.valksor.com/mcp claude mcp add --transport http interslavic https://interslavic.valksor.com/mcp
Or call the JSON APIs
Every server mirrors its MCP tools as a JSON API under
/api on its own host, with interactive docs at its
/api/docs and a machine-readable usage guide at its
/llms.txt — or reach them all through this hub's passthrough
above:
curl "https://latin.valksor.com/api/search?query=amor" curl "https://scythian.valksor.com/api/search?query=bitter&search_language=eng"
LLM usage for this index: /llms.txt