pulsemcp verified Safe content atomic mcp-remote

Figma to Flutter

This Figma-to-Flutter MCP server enables AI assistants to automatically convert Figma designs into Flutter widget code through direct integration with the Figma API. Built with TypeScript and the MCP SDK, it extracts design elements from Figma files, analyzes component structures, and generates corresponding Flutter widgets with proper styling, layout properties, and project organization. The implementation features intelligent design extraction with deduplication of colors, text styles, and components into reusable libraries, automatic categorization of UI elements into Flutter-appropriate widgets (buttons, cards, screens), and generation of complete project structures with proper file organization and imports. It handles complex design hierarchies, converts Figma styling properties to Flutter equivalents, and provides retry mechanisms with rate limiting for robust API interactions, making it particularly useful for Flutter developers who want to accelerate UI development by automatically translating design mockups into production-ready code.

Cognium trust score

78%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: file-system
Source: PulseMCP
Repository: github.com/mhmzdev/figma-flutter-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Figma to Flutter from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"