MCP 服务器

Unified Figma MCP

Coordinates Plumb and Custom Figma MCP backends under one unified interface, exposing backend health and switch prompts because only one active plugin bridge is supported at a time. Currently includes investigation docs, diagnostic probes, and a Stage 2 coordinator runtime.

README

Unified Figma MCP

Unified Figma MCP coordinates Plumb-family and Custom-family Figma capabilities without modifying either original backend.

Correct local path:

C:\Users\rachi\OneDrive\Documents\FIGMA UNIFIED MCP

Stage 4 Status

Stage 4 turns the Stage 3.5 single-plugin proof of concept into a production Unified runtime foundation:

Unified MCP -> CapabilityRegistry -> CommandRouter -> ProtocolAdapter -> CommandQueue -> UnifiedBridge -> UnifiedPlugin -> Figma

Primary Stage 4 tools:

node scripts\unified-probe.mjs unified_capabilities
node scripts\unified-probe.mjs unified_execute '{"capability":"plumb.outline","payload":{}}'
node scripts\unified-probe.mjs unified_execute '{"capability":"custom.node.read","payload":{"depth":1}}'
npm run stage4:live

Supported production runtime capabilities:

plumb.status
plumb.outline
plumb.selection.read
custom.status
custom.node.read
custom.selection.read

All Stage 4 capabilities are read-only. Original Plumb and original Custom are not modified.

Stage 4 docs:

docs/STAGE4_POC_REVIEW.md
docs/STAGE4_ARCHITECTURE.md
docs/UNIFIED_PROTOCOL.md
docs/CAPABILITY_REGISTRY.md
docs/COMMAND_ROUTING.md
docs/RUNTIME_LIFECYCLE.md
docs/STAGE4_TEST_PLAN.md
docs/STAGE4_RESULTS.md

Stage 1 Status

Stage 1 is documentation and verification only. The repo currently contains architecture docs, test results, and a Custom MCP SDK probe. No production coordinator implementation has been added yet.

Key Finding

Plumb and Custom both work as real Figma MCP paths, but the current Figma workflow supports one active MCP plugin bridge at a time. Unified MCP should therefore expose explicit backend health and clear switch prompts.

Docs

docs/CURRENT_SYSTEM.md
docs/PLUMB_ARCHITECTURE.md
docs/CUSTOM_MCP_ARCHITECTURE.md
docs/PROTOCOL_MAP.md
docs/CAPABILITY_MATRIX.md
docs/ARCHITECTURE_OPTIONS.md
docs/FAILURE_ANALYSIS.md
docs/IMPLEMENTATION_RECOMMENDATION.md
docs/TEST_PLAN.md
docs/STAGE1_RESULTS.md

Diagnostic Script

scripts/custom-mcp-sdk-probe.mjs

Example:

node scripts\custom-mcp-sdk-probe.mjs --wait-paired --read --write

The script starts the existing Custom MCP server as a child process, talks MCP over stdio using the MCP SDK installed in FIGMA-CUSTOM-MCP, and optionally verifies status, read, write, and cleanup.

Stage 2 Status

Stage 2 adds the first real Unified MCP coordinator runtime:

npm run start

Diagnostic helpers:

node scripts\unified-probe.mjs unified_status
node scripts\unified-probe.mjs unified_probe_backend '{"backend":"plumb"}'
node scripts\unified-probe.mjs unified_probe_backend '{"backend":"custom"}'
node scripts\unified-live-sequence.mjs

Stage 2 docs:

docs/STAGE2_ARCHITECTURE.md
docs/STAGE2_TEST_PLAN.md
docs/STAGE2_RESULTS.md
docs/BACKEND_ADAPTERS.md
docs/STATUS_MODEL.md
docs/ERROR_MODEL.md

Stage 3 Status

Stage 3 investigated automated backend handoff. Result: AUTOMATED HANDOFF BLOCKED under the current two-plugin architecture. Unified MCP can observe manual backend changes, but it cannot legitimately launch the inactive Figma plugin without a new plugin architecture or fragile UI automation.

Stage 3 docs: