pronounce-mcp — MCP server for the Pronounce dictionary
mcp-name: io.github.anzy-renlab-ai/pronounce
An MCP server that exposes the community pronunciation dictionary at https://pronounce.renlab.ai as tools any MCP-aware client (Claude Desktop, Continue, Zed, ...) can call.
When a user asks an LLM "how do you pronounce kubectl?", the client invokes pronounce("kubectl") and gets back the canonical reading, IPA, alternate readings (if contested), source citation, and a link to the human-readable page — without the LLM having to hallucinate.
Tools
| Tool | What it does |
|---|---|
pronounce(word) |
Look up a single word. Returns IPA, respelling, alts, source URL, confidence, category, notes. |
search_pronunciations(query, limit) |
Find entries by partial match on word or category. |
list_pronunciations(category) |
List all entries, optionally filtered by category (product, cli-tool, acronym, ...). |
Install (Claude Desktop)
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"pronounce": {
"command": "uvx",
"args": ["pronounce-mcp"]
}
}
}
Or with pipx:
pipx install pronounce-mcp
{
"mcpServers": {
"pronounce": { "command": "pronounce-mcp" }
}
}
Restart Claude Desktop. Ask any pronunciation question:
"How do you pronounce kubectl?"
Claude calls pronounce("kubectl") → gets {respelling_us: "koob control", ipa: "/ˈkuːb kənˌtroʊl/", source_label: "Kelsey Hightower (KubeCon)", url: "https://pronounce.renlab.ai/word/kubectl", ...} → answers with the canonical reading plus the citation.
Run the Node implementation from source
A zero-dependency Node (>= 18) implementation of the same server lives in npm/. It is not currently published to npm, so run it from a checkout with node mcp-server/npm/index.js. Use the PyPI package above for a registry-backed one-line install.
Why this is useful
LLMs are bad at pronunciation by default. They've seen the spelling and the IPA, but they confabulate when asked about contested words (GIF? jif or gif?) or project names with non-obvious readings (kubectl is "koob-control", not "kub-cuttle"; Pinia is "pee-nya"; Vite is "veet").
This MCP server gives the LLM a deterministic source: the dictionary is community-maintained, source-citing, and updated continuously. Every contested word has both readings with the rationale. Every "creator-clarified" reading links to where the creator settled it.
Source data
The dictionary is at https://github.com/anzy-renlab-ai/pronounce/blob/main/data/pronunciations.tsv — 1,900+ entries (and growing) across cloud / DevOps, frontend & backend frameworks, AI/ML platforms and research, databases, languages, editors, companies, programmer jargon, and acronyms.
Each entry has 10 columns: word | ipa | respelling_us | alt_ipa | alt_respelling_us | source_url | source_label | category | confidence | notes.
confidence is one of: creator-clarified (source URL documents a creator quote), community-consensus (widely used but no single citable source), or contested (multiple readings in active use).
License
MIT.
Metadata
Release files for pronounce-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pronounce_mcp-0.1.2.tar.gz | 4.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pronounce_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / pronounce_mcp-0.1.2.tar.gz
| Download URL | pronounce_mcp-0.1.2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c274d6eb8383ada2753693fb4e30a7db51325bdcd1786f30f2dc3bbcd73a4f8a
|
|
BLAKE2b-256 checksum How to use checksums |
dedbdad39dbdd108215aaaa535431d70d0938543cd32ab5d4d38dd3766a9168a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / pronounce_mcp-0.1.2-py3-none-any.whl
| Download URL | pronounce_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b320c467dbd6284e1c0d66850c8c6fd3dc37880061d0f0169a2357e2d94fa0ba
|
|
BLAKE2b-256 checksum How to use checksums |
a7bb7c57062885e3a0daa6301fe43ed0f9e36c592bb2cbaa187f955922eedadf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logSecurity for pronounce-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pronounce_mcp-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.