Skip to main content
Once an AI tool is connected to the MCP server, you can work with your silos in plain language. This page collects prompts that work well and shows which tools the assistant uses behind the scenes. You will use: an MCP Key and a connected client. See Connect a Client to set one up.
Start with a Read only key. Create a Read & write key only when you want the assistant to change data.

Explore your silos

Works with a Read only key. For a large silo, the assistant gets a summary of its shape instead of the whole document, and then asks for just the part it needs. You don’t have to do anything differently.

Make changes

Needs a Read & write key. For small changes, the assistant uses patch_silo, which sends JSON Patch operations instead of the whole document. For example, turning on darkMode becomes:
A patch is all or nothing. If one operation fails, nothing is saved.

Walkthrough: seed a silo from your codebase

A common job in Claude Code or Cursor is turning data that lives in your code into a silo your apps can read.
1

Ask the assistant to build and upload the data

The assistant reads the file, converts it to JSON, and calls create_silo with is_public: true and region_name: "sg-01-api".
2

Point your code at the silo

3

Lock the shape in the console

Open the new silo in the console, go to Data & schema, click Enable, and lock the schema. From now on, a write that changes the shape is rejected, whoever sends it. See Schema Lock.
An assistant can read a schema but can’t create, change, or unlock one. Only you can, in the console.

Walkthrough: a safe bulk edit

For changes that touch many values, ask the assistant to show you its plan first.
After you approve, the assistant applies the change with one patch_silo call. If the silo has a locked schema and a new value doesn’t fit, for example a price written as a string, the patch is rejected, nothing is saved, and the assistant is told which value was wrong so it can fix it. You can review every change it made in Logs, where MCP writes carry an (MCP) label.

Tips for good results

  • Name the silo. “my catalog silo” is clearer than “the product data”.
  • Ask for a plan before big changes, as in the bulk edit above.
  • Say the region and access when creating a silo. Otherwise the assistant uses the defaults: private, in api (Germany).
  • Give each tool its own key, so you can remove one without affecting the others.
  • Region changes happen in the console. The MCP server can’t move a silo to another region.