What you can do
Maya's homepage hero already lives on Default Project. The sale landing page should not share those environments. From the agent she names a new project. RuleCMS creates Development, Staging, and Production for it. She registers the marketing site as its own app, then asks for a Development token. The key comes back starting with dev., the same prefix she would copy from the environment home.
The dashboard is the better door for some jobs. The agent is better for others.
- Use the agent when you are already in the chat and you know the project name, the app name, and which environment the site should call.
- Use Overview when you want the project cards, the environment switcher, and the token checkbox in front of you. The walkthrough for those clicks is Projects, Environments & Tokens.
The same permissions as Overview
The agent acts as the RuleCMS account that signed in when you connected MCP. It does not get a side door.
Creating a project or another environment needs Projects at Manage or Admin. Opening an environment home still needs View Project Environment (Staging and Production have their own view groups). Registering an app or creating a token needs Apps and Tokens at Manage or Admin. Saving a project theme needs Project CSS Catalog at Manage. A teammate who can only view will see the same refusal on Overview.
Create the sale project
She is signed in on the team that should own the landing page, and she has Manage Projects.
- Connect RuleCMS in the agent, if you have not. The steps are on MCP.
- Tell the agent the team and a project Name a teammate would recognize. Description is optional.
- Ask it to read the project back. You should see Development, Staging, and Production. No token is created with the project.
- Register the app with a Name, such as “Marketing site”. Description is optional. That is Register App under External App Registry on Overview.
- Ask for a token for that app on Development, and say whether it is enabled. An enabled Development token is what the marketing site uses to preview drafts.
An extra environment, one that is not Development, Staging, or Production, is a separate ask. The name has to be unique on that project. RuleCMS does not create a token for it. Add the token yourself. Because the name is not Staging or Production, that token is stored with a dev. prefix and loads live drafts.
The token for Development
Say enabled or disabled. Leaving that out is refused. The agent sends the secret. For Development, and for any environment whose name is not Staging or Production, RuleCMS stores the key with dev. in front. If the secret already starts with dev., it is not added twice. A Staging or Production token is stored without that prefix. A dev. prefix sent for those two environments is removed.
Only one token can be enabled for the same app and the same environment. Disable the current one before a replacement can be enabled. A disabled token rejects public API requests. The agent cannot delete a project, an app, or a token. Disable the token you do not want sites to use.
To list tokens, name the app or the environment. Naming neither is refused. Pair a dev. token with a draft widget key. That preview is Development Integration. A Staging or Production token pairs with a published key, as on Publishing.
The project theme
The CSS catalog belongs to the project, not to one environment. The first theme, font, or other catalog piece creates it. Maya's dark theme is one condition, the HTML class dark, overriding --background. She left off Include these theme overrides when published widgets are rendered, so the theme sits on the project until she turns inclusion on.
A second create is refused, because the catalog is already there. Change the theme, the fonts, the variables, the classes, the keyframes, the cascade layers, position try, the CSS properties, or the widget chrome. Those are updates to the same catalog. CSS styles are a separate save on the project. The manuals for each piece start at Themes and Projects, Environments & Tokens.
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.
| What you asked for | The tool |
|---|---|
| Create the project | post_t_teamId_p |
| Read that project | get_t_teamId_p_projectId |
| Add an environment | post_t_teamId_p_projectId_e |
| Register an app | post_t_teamId_apps |
| Create a token | post_t_teamId_app_project_env_tokens |
| Enable or disable that token | patch_t_teamId_app_project_env_tokens_token |
| Save the first theme | post_t_teamId_p_projectId_themes |
| Change the theme later | put_t_teamId_p_projectId_themes |
When it does not land
| What you see | What it usually means |
|---|---|
| The agent says you cannot do that | This account is missing Manage Projects, Manage on Apps and Tokens, or Manage on Project CSS Catalog. Overview would say the same thing. |
| An enabled token already exists | That app already has an enabled token on that environment. Disable it, then create or enable the replacement. |
| The catalog already exists | A theme, font, or another catalog piece was saved once. Ask the agent to change that piece. Do not create the catalog again. |
| The environment name already exists | Development, Staging, Production, or a name you already added is taken on this project. Pick another name. |
| A token list was refused | Name the app or the environment. One of those is required. |
What to read next
- MCP — Connect the agent. It signs in as you.
- Projects, Environments & Tokens — The Overview clicks for the same project, app, and token.
- Development Integration — Preview drafts with the
dev.token. - Themes — The condition and the inclusion choice on the project catalog.