mcpbeat Sign in

StyleForge-AI MCP Server

answering

StyleForge-AI is answering right now. Last checked 5 min ago.

Automated design token builder producing clean CSS and Sass assets.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
96 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check StyleForge-AI every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add styleforge-ai --transport http https://styleforge-ai-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "styleforge-ai": {
      "url": "https://styleforge-ai-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.styleforge-ai]
url = "https://styleforge-ai-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "styleforge-ai": {
      "url": "https://styleforge-ai-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "styleforge-ai": {
      "url": "https://styleforge-ai-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://styleforge-ai-mcp.vercel.app/api/mcp sse needs auth 68 ms 5 min ago

Alternatives to StyleForge-AI

same job, measured the same way
StyleSeed Tokenizer
by evozim

Automated design system token generator and export utility.

answering
Mimic AI
by miapre

Builds Figma from your design system: real components and tokens, enforced, learning every build.

66 installs/wk local only
Uiscanner
by mishaovcharenko

Design tokens + a build prompt from any URL, right inside Claude Code, Cursor, and Codex.

47 installs/wk local only
Canva
by mcparmory

Create designs, manage assets, and automate design generation from external workflows

260 installs/wk local only
Design System
by zaklad

Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.

answering
Design Token Bridge MCP
by kenneives

Translate design tokens between Tailwind, Figma, CSS, Material 3, and SwiftUI

79 installs/wk local only
Figma
by mcparmory

Export files, access design data, manage projects, comments, and team assets

246 installs/wk local only
Branding MCP
by forge-space

AI-powered brand identity generation via MCP with design tokens, typography, and logo assets.

108 installs/wk local only

StyleForge-AI — questions

Answers built from our own checks of this server.

Why is there no tool list for StyleForge-AI?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is StyleForge-AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.
How do I connect StyleForge-AI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does StyleForge-AI need an API key?
Yes. Every time we knock, StyleForge-AI answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is StyleForge-AI?
It answers our handshake in 96 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.