MCP Server
The MCP server is a thin, public wrapper around the Names API. Internal-only services (rate limiter, transport plumbing) live in nd-mcp but aren’t part of this contract.
NameDrop publishes a Model Context Protocol server so AI agents can fetch name pronunciations as a first-class capability — not as a screen-scrape.
What the MCP server exposes
Section titled “What the MCP server exposes”| Tool | Purpose |
|---|---|
namedrop_pronounce_guide | Given a name or NameDrop profile URL, returns pronunciation audio URL plus phonetic guide |
Why an MCP server (and not just an API)
Section titled “Why an MCP server (and not just an API)”The Names API alone is enough for typical apps. The MCP server adds:
- Tool surface for agents — Claude, GPT-class agents, and other MCP-capable clients discover the tool through the standard MCP catalog.
- Rate-limit handling — server-side rate limiting + retries that the agent doesn’t have to think about.
- Normalised inputs — accepts raw names, profile URLs, or partial matches; returns a consistent shape.
Quick start (Claude Code)
Section titled “Quick start (Claude Code)”{ "mcpServers": { "namedrop": { "command": "npx", "args": ["@namedrop/mcp"] } }}Reload Claude Code; the namedrop_pronounce_guide tool appears in the tool list.
Quick start (other clients)
Section titled “Quick start (other clients)”The server speaks standard MCP over stdio. Any MCP-compatible client can attach via:
npx @namedrop/mcpWant access?
Section titled “Want access?”Email hello@namedrop.io — we’ll set up an API key for production usage and add you to the early-access list.
Was this page helpful?
Thanks for your feedback!