Skip to main content
Glama
denizzeybek-fe

Insider Design System MCP

by denizzeybek-fe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DS_PATHNoPath to the Insider Design System source code (for component extraction if re-extraction is needed at runtime)
ANALYTICS_FE_PATHNoPath to the analytics-fe codebase (for usage analysis if re-extraction is needed at runtime)

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
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list-componentsB

List all available Design System components, optionally filtered by category

get-componentA

Get detailed information about a specific Design System component in Markdown format.

Returns component documentation in human-readable Markdown format with:
- Props with types, defaults, and descriptions
- Events with payloads
- Examples with code snippets
- Common mistakes and best practices
- Related components

Note: Markdown format provides 77% token savings compared to JSON.
search-componentsA

Search for Design System components by name, description, or category

get-propsA

Get detailed props information for a component with types, defaults, and descriptions

get-eventsA

Get all events emitted by a component with their payloads

get-examplesC

Get code examples for using a component

generate-codeC

Generate Vue component code with the specified props

map-figma-componentB

Map a Figma component name to the corresponding Design System component with default props

optimize-promptA

Transform raw user prompt into MCP-optimized prompt for better Design System integration.

This tool analyzes user intent, identifies components, and generates a structured prompt
that guides Claude to use the right MCP tools in the right order with token awareness.

Example: "bir buton ve dropdown lazım"
→ Returns optimized prompt with tool sequence, token savings estimates, and clear steps
list-figma-mappingsA

List all available Figma component to Design System component mappings

validate-figma-componentA

Check if a Figma component name can be mapped to a Design System component

convert-figma-to-vueB

Convert a Figma frame/screen to Vue component code using Design System components

get-ds-for-figmaC

Get Design System component information for a Figma component name

generate-figma-componentC

Generate Vue code for a single Figma component with specific properties

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
components-listList of all available Design System components
registry-infoDesign System registry metadata and version info
categoriesAll component categories
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

B3.4/5.0

Scored across 14 tools

Disambiguation3/5

Most tools have clear verb+object distinctions, but several overlap: get-component versus get-props/get-events/get-examples, get-ds-for-figma versus map-figma-component, and generate-code versus generate-figma-component. Descriptions clarify intent somewhat, but an agent could easily select the wrong tool for a similar task.

Naming Consistency4/5

Tool names uniformly follow lowercase snake_case with a verb-object structure (list/get/search/generate/map/validate/convert). Minor inconsistencies like get-ds-for-figma and the pair generate-figma-component versus convert-figma-to-vue slightly break the pattern but remain predictable.

Tool Count4/5

14 tools is a reasonable count for a design-system documentation and Figma conversion server. However, some tools feel redundant or consolidatable, such as get-ds-for-figma and map-figma-component, making the set slightly heavier than necessary.

Completeness4/5

The server covers component discovery, detailed documentation, props/events/examples, code generation, and Figma mapping/validation/conversion well. Minor gaps like design tokens, theme variables, or component dependency relationships are missing but not critical for the core workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources