"MCP (Model Context Protocol) requirements and selection" matching MCP servers:

Enables an AI assistant to open 3D model files (STL, 3MF, Bambu Studio and OrcaSlicer projects) in a local browser viewer where the user clicks exact spots to leave feedback. Each note comes back with the part name, millimetre coordinates, surface direction and a numbered screenshot, so the assistant can revise the design and show the new version.

Ask, check and change live Revit models from Claude, Cursor or any MCP client. One undo per change, read-only switch. Revit 2022-2027.

A Model Context Protocol (MCP) server that enhances Figma design integration by adding element position information to API responses, enabling AI assistants to better understand spatial relationships and convert designs to code more accurately.

Converts Lanhu design URLs into AI-ready implementation context including HTML+CSS (Tailwind), image downloads, design tokens, and guidance.

Open, secure runtime that puts Revit, Rhino, Navisworks, and Power BI behind one MCP call center, enabling an AI agent to orchestrate them directly instead of manually dumping data between disconnected apps.

Loads your project's Tailwind CSS config and exposes tools for AI agents to query actual design tokens and validate class names, preventing hallucination of non-existent utilities.

A read-only MCP server that extracts actual Figma prototype flows, transitions, and per-screen interactions so agents can see navigational behavior rather than infer it. It reports explicit source and destination IDs with warnings for unresolved or ambiguous destinations, without guessing or writing back to Figma.

Converts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.

Enables users to generate rigged, game-ready gun models in Blender from parameterized presets or platforms, including attachments, animation clips, fact sheets, and reference-photo validation.

An MCP server that gives AI coding tools access to Figma design data for accurate one-shot implementation of designs.

An MCP server that gives AI coding agents access to Figma design data, enabling pixel-perfect implementation of designs through structured data extraction, image downloads, and design token retrieval.

Exposes tools to ingest FigJam boards, retrieve context summaries, and answer free-form questions about the board content.

Converts Figma design data into structured semantic analysis JSON and screenshots for AI agents to use in design-to-code workflows.

Enables driving Inkscape headlessly from an MCP client, with verified SVG editing, rendering, optimization, and animation tools.

Enables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.

Enables coding agents like Cursor to access Figma design data, fetch layout and styling information, and implement designs in any framework.

Enables Cursor to access Figma design data via MCP, allowing it to fetch simplified layout and styling information to accurately implement designs from Figma files.

Exposes surface-bound annotations placed on a Blender model to AI agents, letting them read pending change requests with stable IDs, revisions, positions and visibility, then submit completion summaries by marker ID after editing. This enables batch, review-oriented workflows where the user approves or rejects each agent change in Blender, without requiring object selection, screenshots, or a fixed port bridge.

Enables AI clients to control a running Blender instance through the Model Context Protocol, allowing scene inspection, object creation and editing, rendering, and execution of Blender Python. It works locally via a WebSocket bridge between the MCP server and a Blender add-on.

Enables Claude and other MCP clients to create and edit vector artwork inside a running Graphite editor, turning SVG into fully editable native layers and supporting export, styling, transforms, selection and layer management. Every operation is delivered as a regular editor message, so undo, selection and the Layers panel behave exactly as with manual edits.