Skip to main content
Glama
sliday

google-fonts-mcp

by sliday

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_fontsA

Search Google Fonts by description, mood, or use case.

Modes:

  • single: Body-suitable fonts for heading + body (default)

  • pair: Proven font pairings with contrast type

  • scale: Typographic scales by use case

Tier filter (A/B/C) applies to single mode only.

generate_typography_systemA

Generate a complete typography system from font selection + scale.

Returns CSS custom properties, Tailwind config, and/or Google Fonts embed HTML. Format: css, tailwind, embed, or all. Weights: semicolon-separated per the css2 API (e.g. "400;700"); variable ranges use ".." (e.g. "100..900"). Legacy comma input is auto-converted.

lookup_fontA

Look up a specific Google Font by exact name. Returns full metadata.

list_scalesA

Return all 8 typographic scales with ratios and use-case recommendations.

list_pairingsA

Return all 73 proven font pairings. Optionally filter by contrast type (Structure, Proportion, Era, Weight).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation4/5

Most tools have clearly distinct purposes: searching, looking up a font, generating a system, and listing scales/pairings. However, search_fonts has 'pair' and 'scale' modes that overlap conceptually with list_pairings and list_scales, which could cause an agent to pick the wrong tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: search_fonts, lookup_font, list_scales, list_pairings, generate_typography_system. The naming is predictable and easy to infer.

Tool Count5/5

Five tools is well-scoped for a Google Fonts typography server. Each tool covers a distinct need: discovery, lookup, scales, pairings, and system generation, without unnecessary bloat.

Completeness5/5

The tool surface covers the full typography workflow: finding fonts, looking up font details, retrieving scales and pairings, and generating typography system output. No major gaps are apparent for the server's stated purpose.

Maintenance

ActivityMaintained
ResponsivenessSlow