eldertongue — Old English dictionary MCP server
A remote Model Context Protocol server that gives
LLM agents and editors read-only access to eldertongue.com, an
Old English (Anglo-Saxon) dictionary built from Wiktionary data.
The dictionary covers roughly 14,000 headword pages, plus reverse
Modern English → Old English lookup and a full Bēowulf verse index. This repository
holds the public-facing documentation, client configuration samples, and an agent skill for
the hosted MCP endpoint. The server itself is a hosted, managed service — there is no code to
run here.
[Eldertongue MCP connector — tool definition quality and endpoint health on Glama]
Who it's for
- Agents and assistants that need to look up, inflect, or disambiguate Old English words
and want citations back to a stable page URL.
- Editors and IDEs (Claude Desktop, Claude Code, Cursor, VS Code) that speak MCP and want a
ready-made reference tool for historical linguistics.
- Developers who prefer plain REST over MCP — every tool has a same-origin REST equivalent
(see the table below).
If you only need to read a definition by hand, the website itself is the fastest route. This
endpoint exists so a program can get structured, citable data.
Project
Packaging
This repository is also a portable Agent Plugins package:
plugin.json holds the manifest, mcp.json declares the hosted Streamable HTTP server, and
skills/old-english-lookup/ contains the agent skill. Clients that implement the format can load
the MCP server and the skill straight from the repository URL.
server.json is the Official MCP Registry manifest for the
hosted endpoint; it is published as io.github.gowinder/eldertongue (version 1.0.0, streamable-http).
Endpoints
All REST paths are rooted at https://eldertongue.com.
Tools
The MCP server exposes five tools. All take a single string argument and return JSON.
Every successful tools/call returns two text content blocks:
- the tool result as pretty-printed JSON — the objects shown under each tool below;
- a fixed source line you can pass straight through to a reader:
A result with "found": false is still a success, so it carries the same two blocks. Only an
error (isError: true) differs: it returns a single text block holding Error: … and no
source line.
1. lookup_headword
Look up an Old English headword. Input { "word": string } — the headword, with or without
macrons (cyning or cȳning). Returns whether it was found, the normalized headword, canonical
page and Wiktionary URLs, part of speech, grammatical gender(s), IPA, syllable split, declension
or verb class, etymology, and a list of senses.
Input:
Response JSON (first content block, excerpt):
senses[] items have definition and tags. verbClass is populated for verbs and null
otherwise. indexable reflects whether the entry is a full indexed headword page.
2. inflect
Return the full declension or conjugation table for a word. Input { "word": string }. The
response has a top-level found / hasInflection flag and an inflection[] array — one entry
per part-of-speech reading that has a table. Each entry carries a partOfSpeech, a
paradigmKind, one or more tables, and a flat cells list; every inflected form has an anchor
URL of the shape https://eldertongue.com/word/<slug>#<cellId>.
Input:
Response JSON (first content block, excerpt):
Structure in brief: inflection[] → tables[] → groups[] → rows[] → cells[], where each
row cell is { label, forms: [{ form, url }] | null }. The flat cells[] array — each item
{ id, label, forms: [{ form, url }] } — is convenient when you just want every form with its id.
3. identify_form
Identify an arbitrary inflected form — e.g. cyninges — and return the analyses that could
explain it. Input { "form": string }. There may be more than one candidate analysis.
Input:
Response JSON (first content block, excerpt):
grammar includes only the grammatical categories the form actually marks — here case and
number; categories that don't apply are omitted rather than nulled.
4. english_to_old_english
Reverse lookup: given a Modern English word, return ranked Old English candidates. Input
{ "word": string }. Candidates are ranked by a data-pipeline score; each carries a short
gloss and a link to its headword page, and the response includes the reverse-lookup page URL.
Input:
Response JSON (first content block, excerpt):
5. beowulf_occurrences
Find where a word appears in Bēowulf. Input { "word": string }. Returns how many times and on
how many lines the word occurs, a per-spelling breakdown, and a list of occurrences with line
number, verse text, and a deep link to the line (https://eldertongue.com/beowulf#l<line>).
occurrencesTotal is the full count; occurrences[] may be a capped window of them.
Input:
Response JSON (first content block, excerpt):
Client configuration
The endpoint speaks MCP over Streamable HTTP at https://eldertongue.com/mcp. There is
nothing to install and no key to set. Copy the sample for your client from configs/ or use the
snippet below.
Claude Desktop and Claude Code
Claude Desktop reads an mcpServers block from its config file
(~/Library/Application Support/Claude/claude_desktop_config.json on macOS,
%APPDATA%\Claude\claude_desktop_config.json on Windows):
Claude Code adds the same remote server from the command line:
The equivalent config lives in .mcp.json at your project root:
Cursor
Add the server to .cursor/mcp.json in your project (or the global Cursor MCP file). Cursor
uses the mcpServers key:
VS Code
VS Code reads MCP servers from .vscode/mcp.json, using the servers key and an explicit
type of http:
Data and licence
The dictionary content is derived from Wiktionary (via the kaikki.org Old English
extraction) and is licensed under
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0).
If you use this data — in an answer, an app, or a dataset — you must:
- Attribute Wiktionary and eldertongue.com.
- Link back to the specific entry page you used, e.g.
eldertongue.com/word/cyning, and to the
attribution page.
- Share derivatives under the same licence (CC BY-SA 4.0).
Code samples and configuration in this repository are licensed under MIT (see
LICENSE). The MIT licence covers the code, not the dictionary data, which stays
under CC BY-SA 4.0.
Privacy and rate limiting
- Read-only. There are no write, upload, or account endpoints. The server only answers
lookups.
- No authentication. No API key, token, or account is required.
- No tracking. Requests are not recorded against a user or used to build a profile.
- Reasonable rate limit. The service applies a reasonable rate limit to keep it available
for everyone. Batch or high-volume clients should expect to queue and back off on
429
responses rather than hammer the endpoint.
Notes for agents
- When you present a result, cite the
pageUrl returned by the tool (or the relevant
formUrl / verse url), so a reader can verify the entry on eldertongue.com.
- Prefer
lookup_headword for a definition, inflect for a full paradigm, identify_form when
you only have a declined or conjugated form, english_to_old_english for English → Old
English, and beowulf_occurrences for textual attestation.
- Old English spelling is not standardized. If a lookup misses, retry without macrons, or try
identify_form on the form you actually have.
- See
skills/old-english-lookup/SKILL.md for a
drop-in agent skill that wraps these tools.