Elegant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELEGANT_GH_TOKEN | Yes | GitHub Personal Access Token for accessing Elegant MCP server resources |
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 |
|---|---|
| get_componentA | Returns the canonical HTML snippet for an Elegant 1.0 component. Much cheaper than reading a full wiki .md file. Use this instead of Read on any component wiki file. |
| get_recipeA | Returns the full recipe for a Shell type (A/B/C/D): required wiki files, CSS load order, scroll model, and shell structure. Read this INSTEAD of LLM-WIKI.md or INDEX.md for page scaffolding. |
| get_shellA | Returns a ready-to-fill HTML skeleton for Shell A/B/C/D with all required CSS/JS links and SLOT comments. Copy-paste this as the base, then fill the SLOTs. |
| get_chart_snippetA | Returns a ready-to-use ElegantEChart.* HTML+JS snippet for a chart type. |
| get_checklistC | Returns the pre-commit checklist for a shell type. Run this before declaring a page done. |
| get_anti_patternsA | Returns the full list of known bottlenecks, their root causes, and fixes. Read this when something looks wrong before patching inline. |
| list_componentsA | Lists all available component names you can pass to get_component. |
| search_wikiA | Full-text search across all Components-Wiki .md files. Returns file name + matching line + 2 lines of context. Use this to find where a specific class, rule, or pattern is documented. |
| get_iconsB | Returns the list of available icon SVG filenames. Optionally filter by a search term. |
| get_full_wiki_fileA | Returns the COMPLETE content of a wiki .md file. Use only when get_component / get_recipe aren't enough (e.g. reading CSS section for a specific variant). Prefer get_component for HTML snippets. |
| setup_projectA | ⚠️ CALL THIS FIRST before building any page. Returns mandatory folder structure, copy commands, icon reference table, CSS/JS link patterns, and critical rules (NO CDN, NO inline CSS, NO inline SVG). Skipping this tool will produce broken output. |
| get_topnavbarA | Returns the COMPLETE TopNavBar HTML ready to paste. Includes both Row 1 (logo, subscription, icons, avatar) and Row 2 (navigation tabs). All icon paths pre-filled. |
| get_page_blueprintA | Returns a detailed visual blueprint of a real Log360 Cloud page — exact layout, component hierarchy, column names, data patterns, chart config, and sidemenu structure. ALWAYS call this before building any page to understand the correct structure. |
| get_screenshotA | Searches 217 real Log360 Cloud product screenshots by keywords. Returns matching image URLs you can view to understand exact layout, colors, spacing, and data patterns. ALWAYS use this to see what a page really looks like before building it. |
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 14 tools
Each tool has a clearly distinct purpose: e.g., `get_component` returns HTML snippets, `get_full_wiki_file` returns full wiki content, `get_recipe` provides shell structure, and `get_shell` provides a skeleton. There is no overlap or ambiguity among the tools.
Most tools follow a consistent `get_` prefix pattern (e.g., get_anti_patterns, get_chart_snippet). However, a few tools like `list_components`, `search_wiki`, and `setup_project` deviate, introducing minor inconsistency while still being readable.
With 14 tools, the set is well-scoped for a domain focused on building pages with Elegant components. Each tool addresses a specific need without redundancy, and the count falls comfortably within the optimal 3-15 range.
The tool surface covers the full workflow for building pages: setup, anti-patterns, components, recipes, shells, charts, icons, screenshots, wiki search, and page blueprints. There are no obvious gaps; it provides everything needed to construct a page correctly.