Install
$ agentstack add mcp-redongreen-uspec ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
uSpec
Generate design system documentation for your UI components, directly from your AI agent.
Describe a component to your agent. uSpec captures it with the uSpec Extract Figma plugin, generates a portable Component Markdown (.md) spec, then renders sections of that spec back into Figma as annotation frames. Works with Figma Console MCP or the native Figma MCP, inside Cursor, Claude Code, or Codex.
> Component Markdown is the source of truth. create-component-md produces one self-contained .md per component covering API, structure, color, and screen-reader behavior — an artifact LLM tools can build from and humans can query. It is generated from a _base.json capture produced by the uSpec Extract Figma plugin (free on the Figma Community; source is open in [figma-plugin/](figma-plugin/)). Every create-* render skill then takes that .md as its required input and renders a section into Figma via your MCP.
What you can generate
| Spec type | What you get | |-----------|--------------| | Component Markdown | One .md per component covering API, structure, color, and screen-reader behavior | | API Spec | Properties, values, defaults, and configuration examples | | Color Annotation | Design token mapping for every element and state | | Structure Spec | Dimensions, spacing, and padding across density and size variants | | Screen Reader Spec | VoiceOver, TalkBack, and ARIA behavior for every element and state | | Motion Spec | Animation timeline bars and easing details from After Effects data | | Component Anatomy | Numbered markers and attribute tables for every element | | Component Properties | Variant axes, boolean toggles, and variable mode exhibits |
Get started
In your project, run:
npx uspec-skills init
The CLI detects whether you are using Cursor, Claude Code, or Codex, installs all skills and references into the right directory, and writes uspecs.config.json. Then ask your agent to run the firstrun skill to extract your Figma template keys.
Full documentation and examples at uSpec.design.
License
MIT — see [LICENSE](LICENSE) for details.
Designed by Ian Guisard.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: redongreen
- Source: redongreen/uSpec
- License: MIT
- Homepage: https://uSpec.design
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.