What you can do
The spring sale needs a banner, and it needs to be easy to turn off. Maya keeps that as JSON on Development: the sale is on, the banner is spring. She is already in the agent. She names the team, the project, and Development, and the agent stores the JSON. RuleCMS assigns the key. She does not invent one.
Two jobs this is for:
- Use the agent when the flag is a sentence in the chat. "Sale on, banner spring, Development." The agent writes the JSON, reads it back, and can promote that same key to Staging when she asks.
- Use the Remote Configurations pages when you want the form in front of you: Configuration Name, Configuration Description, and Configuration Value. The environment home does not show that card yet. Open the environment, then add
/remote-configurationsto the address. Add on that list is/remote-configurations/new.
A new project already has a Default Configuration on Production. Its JSON is enabled and features.welcome. Maya's sale flag is a second configuration, with its own key. Promoting her key leaves the default one where it is.
One key, one environment at a time
The key is the identity. Promote and copy keep it. The JSON, the name, and the description are what move. Development, Staging, and Production can each hold that key, and each copy of the JSON can differ until she promotes.
A German visitor on the sale is a widget decision. This JSON is the flag the team stores beside that. The site embed does not read the flag yet. Publishing a widget stays on Publishing.
| When you reach for it | What happens |
|---|---|
| Promote to Staging | From Development, or from any environment that is not Staging or Production. The same key lands on Staging. If Staging already has that key, its JSON is replaced. |
| Promote to Production | From Staging only. The same key lands on Production. A key that is already there is replaced. Another key on Production is left alone. |
| Copy To | A fork into an environment that is not Staging and not Production, such as a Preview environment you added. Staging and Production refuse a copy and ask for promote. |
The same account, the same permission
The agent acts as the RuleCMS account that signed in when you connected MCP. It does not gain a permission the account lacks on that environment.
View Config can list and open a configuration. Manage Config can create one, change it, and copy it. Admin Config is the group allowed to remove one. Staging uses View Config Staging, Manage Config Staging, and Admin Config Staging. Production uses the Production names. Those groups sit under User Group To Manage Configurations.
Promote to Staging also needs Post Promote To Staging. Promote to Production needs Post Promote To Production. Both sit under Utility Functions on the team's user groups page, the same groups Publishing uses for a promote.
Store the sale flag
- Connect RuleCMS in the agent, if you have not. The steps are on MCP.
- Tell the agent the team, the project, and Development. The JSON is required. A name and a description are optional. Maya's name is Sale flags. Her JSON is the sale and the banner.
- A version is optional. Leave it out, or send one longer than a single character, and RuleCMS stores
1.0.0. A one-character version is stored as1.0.0as well. - Ask the agent to read it back. The key starts with
config-. That key is what you promote. The name is what you read.
On the form, the fields are Configuration Name, Configuration Description, and Configuration Value (JSON). The button is Create Configuration. The value has to be JSON. An empty box stays on the form.
Change it, then move it
- To change the JSON, send the JSON again, with the key. The name and the description stay as they are when you leave them out, including when the configuration never had a description.
- Promote to Staging from Development. Then open Staging and read the same key. The JSON there is the one you just promoted.
- Promote to Production from that Staging copy. Calling it from Development is refused. Production has to be the next step after Staging.
- Copy To when the destination is an environment you created, such as Preview. Name that environment. Staging and Production are not in that list.
The pages do not offer a remove button. Asking the agent to remove a configuration is refused today, even for an account in Admin Config. Add only the JSON you want to keep.
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. Each one still checks the group for that environment.
| What you asked for | The tool |
|---|---|
| List the configurations on an environment | get_t_teamId_p_projectId_e_environmentId_remote_configurations |
| Create one | post_t_teamId_p_projectId_e_environmentId_remote_configurations |
| Read one by its key | get_t_teamId_p_projectId_e_environmentId_remote_configurations_configurationKey |
| Change the JSON, the name, or the description | put_t_teamId_p_projectId_e_environmentId_remote_configurations_configurationKey |
| Remove one | delete_t_teamId_p_projectId_e_environmentId_remote_configurations_configurationKey |
| Copy To another environment | post_t_teamId_p_projectId_e_environmentId_remote_configurations_copy |
| Promote to Staging | post_t_teamId_p_projectId_e_environmentId_remote_configurations_promote |
| Promote to Production | post_t_teamId_p_projectId_e_environmentId_remote_configurations_promote_to_production |
When it does not land
| What you see | What it usually means |
|---|---|
| The agent says you cannot do this on the team | This account is missing View Config, Manage Config, or the Staging or Production version for that environment. The pages would say the same thing. |
| Create was refused | The JSON value was missing. A name by itself is not enough to create one. An update can leave the JSON out, and the stored value stays. |
| Copy to Staging or Production was refused | Those two environments take Promote to Staging and Promote to Production. Copy To is for an environment you added. |
| Promote to Production was refused | The key has to be on Staging first. Promote from Development stops at Staging. |
| Remove was refused | Removal is refused today, including for Admin Config. The list has no remove button. |
What to read next
- MCP — Connect Cursor, and the rest of what an agent can reach.
- Publishing — Promote for widgets, and the same Post Promote To Staging group.
- Projects, Environments & Tokens — Development, Staging, Production, and an environment you add for Copy To.
How this fits
A remote configuration is JSON the team keeps on an environment. The agent reads and writes it as the person who signed in. Composer templates, the ones saved from the composer, are a different store and use View Template and Manage Template. The homepage hero is still a widget. She still publishes that when the page looks right. The sale flag moves by promote, and the embed does not fetch it yet.