Figma MCP Server Now Supports Xcode for Native Apple Development.

Figma announced on LinkedIn that its Model Context Protocol (MCP) server is now supported in Xcode, Apple's integrated development environment. The integration extends Figma's MCP capabilities to native Apple platform developers, allowing them to query design files, export assets, and retrieve component data without leaving their coding environment.

The update targets teams building iOS, macOS, watchOS, and visionOS applications. Developers can now use MCP to pull Figma design specifications directly into Xcode, reducing the friction of context switching between design and code. The integration follows Figma's recent updates to its MCP server, which added slides generation and custom font support.

MCP, originally developed by Anthropic, provides a standardized way for AI assistants and tools to communicate with external data sources. Figma's implementation lets developers connect their design system to coding workflows, enabling programmatic access to frames, layers, styles, and components stored in Figma files.

For teams using Cursor or other AI-powered IDEs alongside Xcode, the MCP server can serve as a bridge between design decisions and implementation. A developer writing SwiftUI code could, in theory, query the MCP server for color tokens or spacing values defined in Figma, ensuring design-code consistency without manual lookups.

The Figma MCP server runs locally and connects to the Figma API. Once configured in Xcode, developers can issue commands to retrieve design data, export images at specific resolutions, or fetch CSS properties from Figma components. The server translates these requests into API calls, returning structured data that can be used in code generation or documentation.

Typical use cases include:

• Pulling typography scales and color palettes into Swift constants
• Exporting icon assets at 1x, 2x, and 3x resolutions for iOS app bundles
• Validating implemented spacing against design specs
• Generating SwiftUI views based on Figma component structures

The integration is particularly relevant for teams adopting design-to-code workflows where designers work in Figma and engineers implement directly in Xcode. Instead of manually translating design values, developers can automate portions of that process through the MCP layer.

Figma's MCP server support now spans multiple development environments. Beyond Xcode, the server works with tools like Claude, Windsurf, and terminal-based workflows. This broad compatibility reflects a larger trend of making design systems programmatically accessible across the development stack.

The Xcode integration arrives as Figma continues investing in developer-facing features. Earlier this year, the company launched Figma Make, which added codebase integration and Git-style version control. The MCP server complements these efforts by providing a lightweight, API-driven alternative for teams that prefer scripting their own design-to-code pipelines.

Developers interested in setting up the Figma MCP server with Xcode can find documentation on Figma's official website. The server requires a Figma account with API access and a local installation of the MCP runtime. Configuration involves adding the server to Xcode's external tools or integrating it into build scripts.