Font Metadata
Let your coding agent query font metadata (families, weights, files) over MCP while you design or implement typography in a product UI.
Overview
io.github.lazymac2x/font-metadata is a MCP server for the Build phase that exposes font metadata to your agent over streamable-http on Cloudflare Workers.
What is this MCP server?
- Remote streamable-http MCP endpoint on Cloudflare Workers (api.lazy-mac.com)
- Server schema v2025-09-29 compatible registration for Claude Code, Cursor, and other MCP clients
- Focused font-metadata tool surface instead of a general design suite
- Version 1.0.0 with GitHub source at lazymac2x/font-metadata-api
- No local worker deploy required when using the hosted remote URL
- MCP server version 1.0.0
- 1 streamable-http remote endpoint
- Hosted on Cloudflare Workers at api.lazy-mac.com
What problem does it solve?
Agents guess font family names and metadata, causing broken imports and inconsistent typography in shipped UI.
Who is it for?
Solo builders wiring Tailwind, CSS, or design tokens who want the agent to look up font facts through MCP instead of hallucinating names.
Skip if: Teams that need full font licensing negotiation, subsetting pipelines, or offline desktop font managers without an API.
What do I get? / Deliverables
Your agent can query structured font metadata during frontend work so typography choices align with real families, weights, and files.
- Registered remote MCP server in your agent config
- Agent-callable font metadata queries during UI implementation
- Traceable v1.0.0 server identity tied to the published schema
Recommended MCP Servers
Journey fit
Typography choices and implementation land in the build phase when solo builders wire real UI, not during abstract idea work. Font metadata directly supports frontend implementation—pairing typefaces, checking available axes, and avoiding guesswork in CSS or design tokens.
How it compares
MCP integration for font lookups, not a Figma plugin or a typography design skill.
Common Questions / FAQ
Who is io.github.lazymac2x/font-metadata for?
Indie developers and agent users who implement web UI and want reliable font metadata available inside Claude Code, Cursor, or other MCP clients.
When should I use io.github.lazymac2x/font-metadata?
Use it while building frontend pages or design systems when you need the agent to verify font families, weights, or related metadata before you commit CSS or asset choices.
How do I add io.github.lazymac2x/font-metadata to my agent?
Register the remote MCP server URL https://api.lazy-mac.com/font-metadata/mcp with streamable-http in your client’s MCP config per the published server.schema.json entry.