Request: MCP ability to search, list and add components and other assets from libraries added to the file

[nwrightau]

It would be incredibly useful if MCP could interact with components and other assets from libraries already added to the current Figma file.

Specifically, I’d love to see support for:

• Searching for components, styles, and other assets from linked libraries
• Listing available components by category or type
• Inserting a selected component from a library into the canvas

This would unlock a much smoother design experience and align MCP more closely with how designers already work in Figma day-to-day.
Let me know if this is technically feasible or if there are Figma plugin limitations to consider, happy to contribute.

Thanks for all your work on this—loving the direction it's going!

[rosdec]

This sounds like an interesting feature, but from my (limited) Figma plugin API, I've not found direct access to the assets library referenced in a Figma file. Sadly.

[nwrightau]

This sounds like an interesting feature, but from my (limited) Figma plugin API, I've not found direct access to the assets library referenced in a Figma file. Sadly.

If there isn't a direct way to do it, it should already be possible via the plugin and existing methods. The plugin would have to specify the library file manually and copy files in-between. The LLM might be able to do this already I've had some success running it across two files simultaneously. If that link was more direct it might be more reliable.

Here's o3's take based on the plugin API:

With a Figma plugin you can programmatically add an instance of any published library component, but there are two important limitations:

• You must already know the component’s key (a permanent ID that you can copy from the component’s “Copy/Paste → Copy as Link” or from the URL).
• The library that contains that component must be enabled for the current file and the user running the plugin must have permission to use it.

What a plugin cannot do

• List or search the contents of a team library—there’s currently no API endpoint for “show me every component in this library.”
• Publish new components to a library or modify an existing remote component.
• Bypass library-access permissions; if the file/user can’t normally insert the component, neither can the plugin.

const COMPONENT_KEY = "1:234";           

// 1. Import the component definition into the current file
const component = await figma.importComponentByKeyAsync(COMPONENT_KEY);

// 2. Create an instance of that component
const instance = component.createInstance();
instance.x = 100;
instance.y = 100;

figma.currentPage.appendChild(instance);
figma.viewport.scrollAndZoomIntoView([instance]);
figma.closePlugin("Component inserted.");