Schemyx MCP

Connect your AI tools to the UI rules they should follow.

Set up Schemyx once, then Codex, Cursor, Claude, and other MCP clients can read the latest theme contracts, component rules, and stack files before they generate or revise UI.

Get Started View Contracts

npx -y @schemyx/mcp@latest

{
  "mcpServers": {
    "schemyx": {
      "command": "npx",
      "args": ["-y", "@schemyx/mcp@latest"],
      "env": {
        "SCHEMYX_API_KEY": "sk_schemyx_..."
      }
    }
  }
}

Theme contract foundComponent rules foundStack adapter ready

Setup

One local bridge for every Schemyx builder.

The builders are where you shape the rules. The MCP is how those rules actually reach the AI tools editing your code.

Create an API key

Use one Schemyx key for the contracts your AI tools should read.

Install the MCP package

Run the public npm package locally through your AI tool config.

Connect your tool

Paste the generated config into Codex, Cursor, Claude Desktop, or another MCP client.

Test the bridge

Ask your agent to read Schemyx before it creates or updates UI.

AI tool setup

Start with connection, then shape the contracts.

This keeps the product from feeling like another site builder. The first job is getting your AI workflow connected. Theme Forge and Component Forge become the control panels your tools read from.

Open Theme Forge Open Component Forge

Codex

Give Codex live access to your Schemyx theme and component contracts while it edits code.

Cursor

Point Cursor at the same MCP server so project UI decisions stay consistent.

Claude Desktop

Use Schemyx contracts as durable design context in Claude-driven workflows.

Local bundles

Drop exported contract files into a repo and let the MCP read local first, server second.

Context your agent can use

Everything important lives in one MCP-readable contract layer.

Schemyx can read local project bundles first and fall back to the server when a team wants synced, account-backed contracts.

Theme contract

Tokens, color system, type scale, spacing, surfaces, and target-stack files.

Component rules

The components AI must build custom, where to use them, and what it should avoid.

Stack adapter

Stack-specific output so agents know how to apply Schemyx in the project they are editing.

Fresh context

Change Schemyx once, then let your AI tool pull the latest specs before it touches UI.

Install command

Ship the bridge as the stable front door.

npx -y @schemyx/mcp@latest