Can the WeWeb MCP see and use components from a linked library?

Ask us anything
1

We keep our design system in its own WeWeb project and link it as a library to our other projects. We build a lot with the WeWeb MCP, and we ran into the following when working in a project that has the library linked:

  • The MCP can’t list the components of the linked library. `listAllComponents` only returns components that live in the project itself.
  • It can’t place or duplicate a library component. Adding an element with a library component’s tag is rejected; only standard elements and local components are accepted.
  • It can read and edit the props of a library component instance that a person has placed in the editor.
  • A library component’s definition (props and structure) can only be read by querying the library project directly.

Because of this, the MCP can’t build a page with library components. The alternatives we see are worse: rebuilding the components in each project (error-prone, and it drifts out of sync with the library) or detaching them from the library (which gives up the automatic updates).

Questions:

  • Is this behavior expected, and is it planned to let the MCP see and place components from linked libraries?
  • Has anyone found a workable way to build with the MCP and linked libraries together?

Thanks! Happy to share more details.

2

i experienced this issue, most times you have to guide your AI model towards it and look for it at that level not project level. I use claude and it ran into this issue until i directed it on how to find it and then saved it into memory for the project, worked for me in claude but might be a different experience for you.

3

It’s possible, but as @iconic says, it’s quite a challenge to reach that level.

What I’ve done is create my own WeWeb skill that I can use across all my projects, and by using Claude for Chrome I can do things that the MCP can’t do, or finds very difficult.

It’s worked out really well for me, to be honest.

4

We have someone experimenting with that now over here to. Feels like a very token heavy method of working.

Would love to hear from someone like @Joyce, @DanielL or @Alexis to get their feedback.

Is it a deliberate choice to keep the MCP out of the of the connected libraries? Or something that they just didn’t get around to.

5

Hey @ginkelb :waving_hand:

It’s a deliberate choice for now :slight_smile: We’re planning a lot of work to improve how design systems work at workspace and project level so still need time to figure out what that will look like before we consider adding related MCP tools.

For now, I think Samuel and Habib’s suggestions can both get you good results.