"Information about Figma, a design and prototyping tool" matching MCP servers:

An MCP server that integrates AI agents with Figma, enabling reading and programmatic modification of designs.

Enables listing top-level frames in a Figma file and fetching a selected frame's rendered PNG, node JSON, and image-fill map into a local output directory.

Enables AI agents to control and export from Figma via WebSocket, with optional Cloudflare tunnel for remote access.

Enables AI coding agents to read Figma frames, components, or links as compact code-oriented specs with downloadable SVG/PNG assets, and to create or edit Figma content such as frames, text, auto-layout, components, variables, annotations, and prototypes (79 tools). It connects a local WebSocket relay and Figma plugin to the agent, keeping everything private on localhost.

Enables AI agents to directly control Figma Desktop via MCP, supporting UI creation, editing, prototyping, and variable management with over 60 tools.

MCP server connecting Claude/Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode.

Enables AI assistants to read and modify Figma designs programmatically through the Model Context Protocol.

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.

Enables writing to Figma from MCP clients like Claude Code without a Figma Dev seat, using a local WebSocket relay and a Figma dev plugin.

Enables local AI agents to generate and edit Figma designs via the Plugin API through a WebSocket relay, with no rate limits and all communication remaining local.

Enables AI agents to manage inventory conversationally: list and look up products, check current stock levels, record inbound and outbound movements idempotently, review movement history, and surface items below their minimum threshold. Every figure is grounded in tool calls rather than model estimation, and invalid operations return explicit error codes the agent can reason about.

Enables MCP-capable IDEs to search 8,214 design-system components, retrieve exact source bundles and semantic tokens, and follow a copy-first handoff workflow with composition validation.

A local bridge that lets MCP clients inspect, export, and modify Figma files through a development Figma plugin.

Exposes GOV.UK Frontend components and Design System patterns and styles as MCP resources for use with AI assistants.

A lightweight MCP server that enables AI assistants to execute local development tools and retrieve system status with low latency over stdio or HTTP.

An MCP server that provides AI clients with access to developer documentation via llms.txt files. Exposes tools, resources, and prompts.

Deterministic encode, decode, hash and convert for agents, on the same pipeline engine as the String Utility Belt web app, CLI and editor extensions: a pipeline built and checked in the browser runs unchanged from its share link. Base64/hex/URL, JWT, hashes, JSON/YAML/CSV/XML, dates and regex; tools to search, describe and run utilities or whole pipelines, and to detect input formats. Runs locally

Enables AI assistants to perform Google searches with real, resolvable sources and transparent search terms.

MCP server for overseer.nvim — gives any MCP-capable coding agent running inside Neovim (Claude Code, Codex, Gemini CLI, opencode) the same visibility and control over tasks the user has: list, run, tail, restart, stop. Agent-started dev servers land in the user's own task list instead of becoming invisible orphaned processes.

Lets AI assistants discover public Socrata open-data portals, search their datasets, inspect schemas, and run bounded read-only SoQL queries to answer questions with live government data. All access is strictly read-only and results come straight from the publisher's portal.