What you can do
Maya's developers already shipped a React hero. On Component Libraries she would click Add Library, type the Library ID acme, the version, and a short description, and set Active. From an agent she names the team and those same fields. The library shows on the same list.
The page is the better door for some jobs. The agent is better for others.
- Use the agent when you already know the Library ID and the version, and you are in the chat. You do not leave the conversation to find the team page.
- Use Component Libraries when you want the list, when you are comparing version and Trust, or when you are about to drag the card and want the composer open.
Registering does not install the package, and it does not put the card on the palette by itself. RuleCMS still has to enable it. That request, the npm package, and the libraries map her site types are on Build and enable.
The same library, the same permission
The agent does not get a side door. It acts as the RuleCMS account that signed in when you connected MCP.
View Component Libraries can open the list and one library. Manage Component Libraries can register and update. That is the same pair as Add Library and Edit. A teammate who only has View can look, and still cannot register.
Ask AI in the composer is not this. It can drop a card from a library the team already has enabled. It cannot register one.
How a Library ID thinks
The Library ID is the name other teams must not collide with. acme on Maya's team and acme anywhere else in RuleCMS are the same id, so the second registration is refused. You cannot change it later. The widget records it beside the component, as in acme/hero-banner.
It is 3–64 characters, starts with a lowercase letter, and uses only lowercase letters, numbers, and hyphens. A title with spaces, such as "MCP Test Library", is not an id. Put those words in the Description. The description is what the list shows next to the id. Version is required, for the team's reference — for example 1.0.0. The composer still runs the version RuleCMS enabled.
Trust, the package address, and the integrity hash are not yours to set. A new library stays untrusted until RuleCMS enables it. The agent has no field for those, and the page does not offer them on the form either.
Active is the normal status. Disabled hides the library from the composer. It does not delete widget JSON that already names the hero. Turn it back to Active and the card can return. Anything else is refused.
Ask for part of the id, the version, or the description and the list can narrow to that library. A created or updated date is optional, and the start has to be on or before the end.
Register Maya's hero
The package is already enabled. Maya has Manage Component Libraries. The id she was given is acme.
- Connect RuleCMS in the agent, if you have not. The steps are on MCP.
- Tell the agent the team, the Library ID, and the version. Description is optional. Status is Active unless you are hiding it. If you also pass the team id inside the details, it has to be the same team.
- Open Component Libraries. The row shows the id, the version, the description, Active, and Trust. Trust is still untrusted until enablement says otherwise.
- Refresh any open composer. On the Production Default Widget, stay on Components. Her library is its own group once the package is live. Drag the hero the way you drag Image, then publish.
Change the version, the description, or the status
Edit on the list is this update. Send the Library ID as it already is, and the version again even when only the description changes. The id stays locked. A different id in the details is refused, and the row is left as it was.
Disabled is how you take the card off the palette without deleting the library. Active puts it back. The host libraries map is unchanged either way. That map is on Component Libraries.
Names you may see
You do not have to type these. They are the labels in the agent's tool list, if you open it. Register and update still check Manage Component Libraries.
| What you asked for | The tool |
|---|---|
| The team's libraries | get_t_teamId_component_libraries |
| Register a Library ID | post_t_teamId_component_libraries |
| One library | get_t_teamId_component_libraries_libraryId |
| Change version, description, or status | put_t_teamId_component_libraries_libraryId |
When it does not land
| What you see | What it usually means |
|---|---|
| The agent says you cannot register | This account does not have Manage Component Libraries on that team, or it is not a member. View Libraries is the same limit on the page. |
| The Library ID is already taken | That id exists on this team or on any other team in RuleCMS. Pick a different id. You cannot rename the one that exists. |
| The id was rejected | It is shorter than 3 characters, longer than 64, starts with a number or a hyphen, or contains a space, a capital letter, or anything other than a lowercase letter, a number, or a hyphen. |
| Version is required | Create and update both need a version. An update that only changes the description still sends the version the row already has. |
| The palette group is missing | The row can be Active and the card still absent. The package is not enabled yet, or this composer tab was opened before the registration. Refresh, and read Build and enable. |
What to read next
- MCP — Connect Cursor, and the rest of what an agent can reach.
- Component Libraries — Add Library on the team page, Active and Disabled, and where the card sits beside Image.
- Build and enable — The package, the enablement request, and the host
librariesmap. - Ask AI — Drop a card the team already has enabled. It cannot register one.