Galerne documentation
Galerne is a headless CMS hosted in the European Union. You describe your content model in code, people edit content in the studio, sites read it through a JSON API, and agents read and write it through an MCP server. Every project has its own database.
How the parts fit#
| Part | What it is | Where |
|---|---|---|
| Studio | The editing app: documents, media, branches, reviews, comments, settings | https://studio.galerne.cloud |
| API | Delivery, writes, media, webhooks, export and import, per project | https://api.galerne.cloud/p/<project>/v1 |
| MCP server | The same tools for agents, over streamable HTTP | https://api.galerne.cloud/p/<project>/mcp |
| CLI | galerne: schema deploys, content, branches, export, import, a local MCP server | npm i -g @galerne/cli |
| Client | A typed TypeScript client with no runtime dependencies, plus small Python and PHP clients | npm i @galerne/client |
The API, the MCP server and the CLI share one tool registry: one definition per operation, with the same inputs, permissions and errors everywhere. The MCP tools page lists all of them.
Start here#
- Quickstart: create a project, deploy a schema, query it from a site.
- Agent quickstart: create a project and a token, give one prompt with your brief to an agent, and it builds and publishes the whole site.
- Full site tutorial: a hosted site with two languages, a GitHub data source, review and a release, by hand or with an agent.
- Schema: every field type and option of
galerne.config.ts. - Query API: filters, ordering, projections, references, languages and branches.
- Agents and permissions: connect Claude, Cursor or ChatGPT, and set what each agent may do.
- Branches and review: how changes wait, merge and go live.
Everything Galerne does walks through each capability with a short example.
By topic#
- Content: schema, query API, media, languages and translations, the studio.
- Workflow: branches and review, comments and history, scheduling and releases.
- Agents: agents and permissions, MCP tools.
- Integrate: HTTP API, clients, Next.js kit, webhooks, event stream, data sources, CLI, site settings, visual editing.
- Sites: sites and code, site template, design browser.
- Move: migrating, export format.
- Account: members and tokens, SSO and SCIM, limits and plans, billing.
Words we use#
- Project: one content space with its own database, members, tokens and plan. Its slug appears in every URL.
- Document: one entry of a type, with a draft and, once published, a published version.
- Branch: a set of changes that waits until someone promotes it into
main.mainis the live content. - Perspective:
publishedreads what sites see;draftsreads the latest edits. - Member: a person or an agent in a project, with a role.
- Token: a
gal_…secret that acts as a member or as the project, with scopes.
For agents#
Every page of these docs is also plain Markdown: add .md to the URL, or read llms.txt for the index and llms-full.txt for everything in one file.