Skip to main content
Glama
keyline-icons

Keyline Icons

Official
by keyline-icons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_iconsA

Find icons by name. Returns matching names and which of the four styles each one has. Names are kebab-case and compounds read base-first, so a mail icon with a tick is mail-check, not check-mail. Search the base word to find a family. Word order does not matter and a component name from another set is accepted as written, so CheckCircle2 finds circle-check. Trust an empty result: it means the set has no such icon.

get_iconB

The full SVG source for one icon, ready to paste. Colour comes from currentColor, so it inherits whatever text colour is in scope.

get_react_usageA

The import line and JSX for one icon from @keyline-icons/react. Each style is its own entry point because they do not cover the same icons, and sharp is one segment further along: @keyline-icons/react/sharp and /sharp/duotone. The export is called the same thing either way.

describe_setA

What this set is: how many icons, which styles, and the rule that decides which icons have which style. Call this first when deciding whether the set covers what you need.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search_icons finds icons by name, get_icon retrieves SVG source, get_react_usage retrieves React import/JSX, and describe_set explains the set. No two tools overlap in output or intent, and descriptions make the boundaries explicit.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: search_icons, get_icon, get_react_usage, describe_set. The verbs are clear and the naming convention is uniform throughout.

Tool Count5/5

With 4 tools, the set is well-scoped for an icon library: discovery, retrieval in two formats, and set description. Each tool earns its place without redundancy or unnecessary bloat.

Completeness4/5

The core workflows—search, SVG retrieval, React usage, and set overview—are covered. A minor gap exists in browsing or listing all icons (e.g., no list-all or filter-by-style tool), but agents can work around it via search queries.

Resources