google-fonts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_FONTS_API_KEY | Yes | Google Fonts API key. Required for fetching font data from the Google Fonts Web Fonts Developer API. Without it, tool calls will return errors. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fontsA | Search Google Fonts by family name and/or category. Results are sorted by popularity. Provide at least one of query or category. |
| get_font_detailsA | Get full metadata for a Google Fonts family: category, variants, subsets, version and last modified date. |
| preview_textA | Render sample text in a Google Font. Returns a self-contained HTML page. The weight/italic combination must exist in the family. |
| get_embed_codeB | Get the HTML link tags and CSS font-family declaration to use a Google Font on a web page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: finding fonts, inspecting metadata, previewing text, and generating embed code. There is no functional overlap between any of the tools.
All tool names follow a consistent verb_noun snake_case pattern: search_fonts, get_font_details, preview_text, get_embed_code. This makes the toolset predictable and easy to navigate.
Four tools is well-scoped for a Google Fonts MCP server. Each tool covers a distinct stage in the font selection and integration workflow without redundancy.
The toolset covers the full practical lifecycle: discovering fonts, examining their metadata, previewing custom text, and obtaining integration code. No critical workflow is missing for typical font lookup and embedding use cases.