Skip to main content
Glama

Eidova MCP

Design-system selection, real React components, and practical UI review for coding agents. Eight curated families retain all 31 registry IDs. Core exposes 13 typed read-only tools; full keeps 42 public tools and 43 owner tools.

The OpenDesign resource library adds 152 design references and 169 skill entries with original files, hashes and license notices. Use search-resources, then read-resource to read manifests and companion files in any tool-capable client. Native MCP resource reads are also supported. The website reads and downloads the same files and copies an agent prompt. Reference packages remain separate from installable Eidova React kits.

The Studio integration adds an own-backend team workspace, version-checked files, feedback, fourteen opt-in stdio tools, watched file sync, history/restore, presence, sharing and access recovery. --native-studio combines an installed native engine's tools and brief resources with Eidova's stdio tools. Full OpenDesign feature parity is incomplete: the native runtime is source-only here, and its cloud collaboration has not been replaced. See the parity matrix.

0.2.0 is a release candidate, not a published npm package. Verify the website, full HTTP endpoint and /mcp/core against the matching deployed version. Hosted core URLs and new specimens need the coordinated release; local checks alone do not certify deployment.

Run locally

Use Node 22 or newer:

npm ci
npm run build
npm start
codex mcp add eidova --url http://localhost:3000/mcp/core

Use /mcp for full. Public catalog, extraction, guidance and reviews need no account or key. Client setup covers Codex, Claude Code/Desktop, Cursor and VS Code, with verification scope stated explicitly.

For stdio use an absolute path, independently of your client's working directory:

node /absolute/path/eidova-mcp/dist/stdio.js --profile core
node /absolute/path/eidova-mcp/dist/stdio.js doctor

Stdio defaults to full. --help and --version print CLI information; doctor checks bundled assets without credentials or network requests. Before publication, run npm pack and install the resulting tarball in your consumer environment. Its installed executable is eidova-mcp.

Related MCP server: weave-design-system-mcp

First useful tasks

  • “Find a distinctive family for this settings screen. Preserve our existing design if present and retrieve only the components we need.”

  • “Extract this supplied brand CSS and extend the existing interface consistently.”

  • “Review this form's source and copy. Use rendered DOM evidence for spacing and give specific repairs.”

Search returns compact family summaries. Retrieve a selected kit with target: "react" and a component name/list; its shadcn command resolves real source and dependencies. In an initialized React/Tailwind 4 project:

npx shadcn@latest add http://localhost:3000/registry/linear/button.json

The family recipes explain material, typography, geometry and density. The website puts installation in the hero and keeps its own appearance fixed. View components opens a separate viewer of actual Button, Input, Card, Dialog, Table and Sidebar source. Variants have exact token links and an explicitly labelled family specimen.

Context cost

Full public discovery falls from 125,752 to 51,503 UTF-8 bytes; core discovery is 19,237 bytes. All six fixed full-profile workflows meet the 50% reduction gate. These are compact JSON protocol bytes; model token counts and actual client context traces were not measured. See benchmark scope.

Detailed guidance is at design://workflow/v1, with principle/review resources and three optional prompts. Ordinary tools work without these resources/prompts. Choose full for private mutation and specialist guidance; core cannot call tools absent from its discovery.

Persistence and boundaries

Saving themes or team/project rules over HTTP requires a private capability key from POST /api/workspace-key, sent as Authorization: Bearer <key>. Anyone with that key can edit its workspace. Keys have no email recovery, rotation or revocation. Public custom-theme registry URLs intentionally reveal theme configuration; private rules stay owner-scoped and uncached.

Local state defaults to .open-design/state under the working directory. Set EIDOVA_STATE_DIR for durable state and EIDOVA_BASE_URL for the HTTP origin. Hosted persistence uses private Vercel Blob conditional writes, never ephemeral function disk.

The deterministic core needs no external language model. URL extraction fetches bounded public CSS without rendering pages. Source review requires inline content; spacing measures supplied rendered geometry. DTCG export is a documented 2025.10 typed subset. Reviews apply to their evidence and are not accessibility certification.

Carry the selected theme between agent sessions with its portable DESIGN.md. Catalog kits link to design://systems/<id>/design.md and a matching HTTP download, containing exact tokens, source CSS hash, component inventory and usage rules. Search explains family fit and tradeoffs and accepts required component names. The site's component viewer offers a selected-theme prompt and document download. Reference study and scope.

Hosted AI generation, proprietary inspiration, vendor accounts, native/Shopify install kits, credential administration and trusted dashboard browser receipts remain outside this release. The opt-in private archive serves an owner's existing saved responses offline; archived files are excluded from distribution.

Verify and maintain

npm run build:upstream
npm run check
npm test
npm run build
npm run smoke:stdio
npm run smoke:package
npm run benchmark -- --check
npm run audit:themes

npm run verify:consumers uses the local registry and actual shadcn CLI in six disposable Vite/Next consumers. Website checks are in deployment. Edit content/library.json or use the content importer; restart to load changes.

Read the API, candidate verification, implementation status and security policy. Eidova is the selected name; hosted-domain and package ownership are still unverified.

Eidova replaces Open Design. New configuration uses EIDOVA_*; existing OPEN_DESIGN_* settings remain fallback aliases. Local .open-design/state and the private Blob open-design/state prefix are retained so saved workspaces remain accessible. Old review-rule resource links still resolve to the renamed rules. Existing GitHub and Vercel URLs stay in use until the coordinated hosted rename is verified.

This independent MIT project is unaffiliated with Better Design. Copyright, Tabler's embedded SVG license and Lucide's ISC notice are retained in NOTICE and bundled licenses. Supplemental icons use local Lucide; some specialist registry components retain their original Iconify dependencies.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
      5
      83 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.
      13 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search a fully local catalog of 21st-style shadcn components via full-text search, inspect individual records, generate reusable build prompts, retrieve install steps, and fetch design tokens for aesthetic keywords. Runs entirely offline over stdio with no API keys, paywalls, or rate limits.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to read ground truth about a React design system — components, props, cva variants, tokens and docs — over MCP so they write UI that matches it. It also exposes a check_ui linter agents run on their own output, returning rule ids, locations and concrete fixes before review.
      5
      183 npm
      20
      MIT