Figma’s Dev Mode is built to streamline the handoff between design and development. But there’s one feature that quietly powers collaboration in the background: Multi-Cursor Presence (MCP).
If you’ve ever spotted another teammate’s name and colored cursor while inspecting a component, you’ve already seen it in action.
In this article, we’ll break down how MCP works inside Dev Mode—and how to use it to make your dev collaboration feel more like pair programming than a handoff.
🔄 What Is Multi-Cursor Presence in Dev Mode?
MCP in Dev Mode refers to the real-time visibility of other users’ cursors—specifically when they’re interacting with a design file from the developer view.
You’ll see:
- A colored cursor with their name and role
- Cursor movement when they inspect or select elements
- Viewport tracking if you follow their avatar
This means devs and designers can watch each other work, offer quick feedback, or debug layout issues in sync.
🔍 What’s Different About MCP in Dev Mode?
Compared to Figma’s standard canvas mode, Dev Mode does a few smart things:
| Feature | Canvas Mode | Dev Mode |
|---|---|---|
| Cursor visibility | Always shown | Only shown during interaction |
| Context shown | No dev specs | Inspect mode + tokens visible |
| Designed for | Design collaboration | Developer inspection + handoff |
The goal? Less distraction, more precision.
💡 Use Cases That MCP Unlocks for Developers
- Live bug triaging: A developer hovers over a broken button, while the designer watches and updates the component in real time.
- Asynchronous handoff: A dev tags a teammate and points to a component they need clarified—no meeting needed.
- Onboarding junior engineers: Let them follow your cursor and observe how to read design specs, tokens, and spacing.
- Design system exploration: Product engineers can explore nested variants and tokens while designers help guide them visually.
👥 Cursor + Comments = Dev Conversations
In Dev Mode, the cursor becomes a live pointer and a conversation starter. Instead of sending screenshots, devs can just say:
“Look at where my cursor is—I think the padding’s off.”
It’s fast. Contextual. Frictionless.
🧩 Tips for Using MCP Effectively in Dev Mode
- Use “Follow mode” when reviewing layout together.
- Encourage devs to move their cursors to show what they’re referring to during async chats.
- Toggle MCP off if it gets too busy during deep dev inspection.
🔕 Want to Hide Cursors?
Click your avatar in the top-right and select “Hide Cursors”—this works in Dev Mode too.
You’ll stop seeing others’ cursors, but you can still inspect everything independently.
🧠 Final Thought: MCP Is the Bridge, Not the Noise
Figma’s Multi-Cursor Presence is more than a visual feature—it’s a lightweight communication channel. In Dev Mode, it becomes a bridge between intent and implementation.
When used intentionally, it reduces meetings, speeds up collaboration, and gives developers confidence they’re building things right.
Designilo 