Skip to main content
Glama
alexalexalex222

io.github.alexalexalex222/frontend-design-loop-mcp

by alexalexalex222
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
frontend_design_loop_solve

Generate multiple patch candidates, run gates, (optionally) run vision, pick a winner.

Notes:

  • The tool operates on a target git repo (repo_path), not on this MCP repo.

  • By default it does NOT apply changes; it returns a winner patch (git diff) you can apply.

frontend_design_loop_design

Design-first wrapper around frontend_design_loop_solve.

Use this when you want Frontend Design Loop to actively improve the UI, not just verify a host-authored patch bundle.

frontend_design_loop_evalD

MCP tool wrapper for _frontend_design_loop_eval_impl.

Returns:

  • JSON summary (TextContent)

  • Optional vision instructions (TextContent) when vision_provider=client

  • Optional screenshots as ImageContent (base64) so Claude can use built-in vision

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

C2.3/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools. The tool's purpose is singular and unambiguous.

Naming Consistency5/5

With a single tool, naming consistency is trivially perfect. The name uses a descriptive underscore-separated pattern.

Tool Count2/5

A single tool for a 'frontend design loop' is far too few. The server promises a loop of design activities but only provides evaluation, missing creation, modification, or iteration tools.

Completeness1/5

The tool surface is severely incomplete. A design loop typically involves multiple steps (create, review, modify, test), but only an evaluation tool is provided, leaving critical gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources