Reference Data Mcp Server
Give your coding agent instant lookup tools for countries, timezones, HTTP codes, MIME types, units, and constants while you implement APIs and configs.
Overview
Reference Data MCP Server is a Build-phase MCP server that serves countries, timezones, HTTP codes, MIME types, units, elements, and constants to your AI coding agent.
What is this MCP server?
- Lookup countries, timezones, chemical elements, and physical constants without leaving the agent
- HTTP status code and MIME type reference for API and content-type work
- Unit conversion tools for specs, docs, and backend logic
- Runs via stdio or streamable-http on Bun (npm @cyanheads/reference-data-mcp-server v0.1.9)
- Optional MCP_LOG_LEVEL for debug during local MCP wiring
- Server version 0.1.9 on npm as @cyanheads/reference-data-mcp-server
- Two transports: stdio and streamable-http (default http://localhost:3010/mcp)
- Seven described reference domains: countries, timezones, elements, constants, HTTP status codes, unit conversion, MIME t
Community signal: 1 GitHub stars.
What problem does it solve?
Agents routinely invent wrong country codes, MIME types, and unit conversions when you are mid-implementation and do not want to tab out to documentation.
Who is it for?
Indie builders wiring internationalization, HTTP APIs, file uploads, or science-adjacent features who want MCP-backed facts in Claude Code or Cursor.
Skip if: Teams that only need one-off lookups in a browser or builders who require live market or regulatory feeds instead of static reference tables.
What do I get? / Deliverables
After you register the server, your agent can call dedicated lookup tools so reference answers stay consistent across API work, configs, and docs.
- MCP tool access to countries, timezones, elements, constants, HTTP codes, MIME types, and conversions
- Local stdio or streamable-http MCP endpoint for your agent session
Recommended MCP Servers
Journey fit
Reference lookups land in the Build phase because solo builders wire them into features, env configs, and API layers—not during early ideation. Integrations is the canonical shelf: the server exposes MCP tools that plug into Claude Code, Cursor, and Codex alongside other dev MCPs.
How it compares
Structured reference MCP tools, not a web-scraping or search agent skill.
Common Questions / FAQ
Who is Reference Data MCP Server for?
It is for solo and indie developers using Claude Code, Cursor, Codex, or Windsurf who want reliable reference data exposed as MCP tools during product builds.
When should I use Reference Data MCP Server?
Use it while implementing backends, integrations, or agent workflows whenever you need countries, timezones, status codes, MIME types, units, or constants without guessing.
How do I add Reference Data MCP Server to my agent?
Add the npm package @cyanheads/reference-data-mcp-server to your MCP config with Bun, run start:stdio for local stdio or point streamable-http at the documented localhost URL, and set MCP_LOG_LEVEL if you need debug logs.