# Galerne > Galerne is a headless CMS hosted in the European Union, where people and AI agents edit the same content. Each project has an MCP server, content branches with review, a JSON query API, webhooks, and import and export to other CMSs. Agents connect to `https://api.galerne.cloud/p//mcp` (streamable HTTP, OAuth or a project token), or run `galerne mcp` locally over stdio. Agents write on a branch and a person reviews and promotes it. Galerne runs no language model: your agent brings its own. Every page below is plain Markdown. ## Start - [Galerne documentation](https://www.galerne.eu/docs/index.md): What Galerne is, how its parts fit together, and where to start. - [Quickstart](https://www.galerne.eu/docs/quickstart.md): Create a project, write galerne.config.ts, deploy the schema, add content and query it from a site. - [Build a whole site with an agent](https://www.galerne.eu/docs/agent-quickstart.md): Create a project and a token, give one prompt with your brief to an agent in a terminal, and it builds and publishes the whole site in one go. - [Build a hosted site from start to finish](https://www.galerne.eu/docs/tutorial.md): A tutorial that builds the site of a small design studio on Galerne, from an empty project to a live site on Tramontane with two languages, data sources from GitHub and OpenAgenda, a code change under review and a scheduled release. Every step works by hand or with an agent. ## Content - [Schema reference](https://www.galerne.eu/docs/schema.md): Every field type of galerne.config.ts with its options, validation rules, languages, singletons, blocks, the studio structure and the built-in guidelines type. - [Query API](https://www.galerne.eu/docs/query.md): Find documents with a JSON filter, order and page them, pick fields, follow references, choose a language and a rich text format, and read drafts or other branches. - [Media](https://www.galerne.eu/docs/media.md): Upload images and files, describe them, resize and convert images with URL parameters, and stream video with Range requests. - [Languages and translations](https://www.galerne.eu/docs/translations.md): Declare languages, translate per field or per document, read one language with a fallback, find missing and outdated translations, limit translators to their language, let agents translate on a branch, and route languages in Next.js. - [The studio](https://www.galerne.eu/docs/studio.md): What the Galerne studio does: live co-editing with presence, document lists with views and bulk actions, the editor and its panels, the media library, branches and reviews, the design tab, custom inputs and every settings page. ## Workflow - [Branches and review](https://www.galerne.eu/docs/branches.md): How content branches work, how promotion merges text by character and reports conflicts, how reviews, releases, scheduling and rollbacks fit together. - [Comments and history](https://www.galerne.eu/docs/comments-history.md): Comment on documents, single fields and branches, mention people, assign tasks with due dates, read who changed what and when, compare versions field by field, and restore a document or some of its fields. - [Scheduled publishing and releases](https://www.galerne.eu/docs/scheduling.md): Publish or unpublish a document at a set time, group changes into a release that goes live together at its publish time, and what happens when the time comes. ## Agents - [Agents and permissions](https://www.galerne.eu/docs/agents.md): Connect Claude, Cursor, ChatGPT or your own agent to a project's MCP server, and control what each person, agent and token may do with roles, scopes and agent rules. - [MCP tools](https://www.galerne.eu/docs/tools.md): Reference of the 79 tools served by each project's MCP server and HTTP API, with inputs, permissions and plans, generated from the registry. ## Integrate - [HTTP API](https://www.galerne.eu/docs/api.md): Authentication, errors, limits and every route of the Galerne HTTP API, generated from the tool registry. - [Clients for TypeScript, Python and PHP](https://www.galerne.eu/docs/client.md): The typed TypeScript client with types inferred from galerne.config.ts, and the small Python and PHP clients: queries, documents, every tool by name, media, export, import, errors and webhook signatures. - [Next.js kit](https://www.galerne.eu/docs/nextjs.md): Build a Next.js 16 site on Galerne with @galerne/next. Queries are cached and tagged with what they read, publishing purges exactly those pages, and editors preview drafts next to the editor. - [Webhooks and events](https://www.galerne.eu/docs/webhooks.md): Every event Galerne emits, webhook filters, the payload, the t=…,v1=… signature with verification in TypeScript and Python, retries, and the event stream. - [Event stream](https://www.galerne.eu/docs/events.md): Follow every event of a project live over Server-Sent Events, resume after a disconnect, filter by type, and list recent events over HTTP. - [Data sources](https://www.galerne.eu/docs/sources.md): Sync an external JSON API into Galerne docs on a schedule or a webhook, with a declarative mapping, field ownership, overrides that survive syncs, review mode, and the source tools. - [CLI](https://www.galerne.eu/docs/cli.md): The galerne command line tool: log in, write and deploy the schema, manage content and branches, export and import, and run a local MCP server. - [Site settings](https://www.galerne.eu/docs/site.md): Tell Galerne where your site lives so it can preview drafts next to the editor, purge the Tramontane CDN on publish, serve llms.txt and Markdown copies of published documents, and show page views per document. - [Visual editing](https://www.galerne.eu/docs/visual-editing.md): Mark elements of a preview with data-galerne-edit and load the overlay script, so editors open the right field in the studio from the page itself. ## Sites - [Sites and code](https://www.galerne.eu/docs/sites.md): Let Galerne host your website. One action creates a git repo from a site template and a site on Tramontane, then agents change the code on branches through MCP and people review code and content together. - [Site template](https://www.galerne.eu/docs/site-template.md): The Next.js sites hosted projects start from. The starter has pages built from 16 blocks, a blog, people, two languages, previews, a design browser and one file of design tokens. The bare template starts from a project's own content model. - [Design browser](https://www.galerne.eu/docs/design-browser.md): Every token, atom, component and block of a site, rendered by the site itself at /_design, with variants, controls, light and dark, languages and widths. Designers edit tokens from the studio and agents read the components through MCP. ## Move - [Migrating to Galerne](https://www.galerne.eu/docs/migrate.md): How imports and exports between Galerne and other CMSs work, the CLI and tool options, the report, re-runs and sync, and what each direction loses. - [Migrate from Sanity](https://www.galerne.eu/docs/migrate-sanity.md): Import a Sanity dataset into Galerne from the export API, the query API or a file, and export Galerne content as a Sanity dataset: options, mapping and what each direction loses. - [Migrate from Contentful](https://www.galerne.eu/docs/migrate-contentful.md): Import a Contentful space into Galerne from a contentful-cli export, and export Galerne content for contentful space import: options, mapping and what each direction loses. - [Migrate from Storyblok](https://www.galerne.eu/docs/migrate-storyblok.md): Import a Storyblok space into Galerne from the delivery API, with components from the Management API, or from a file, and export Galerne content as Storyblok JSON: options, mapping and losses. - [Migrate from WordPress](https://www.galerne.eu/docs/migrate-wordpress.md): Import a WordPress site into Galerne from a WXR export file, and export Galerne content as a WXR file: options, how posts, pages, media, terms and authors map, and the losses. - [Migrate from Payload](https://www.galerne.eu/docs/migrate-payload.md): Import Payload collections and globals into Galerne from the REST API or a file, with Lexical and Slate rich text, and export Galerne content as Payload data, configs and a seed script. - [Migrate from Markdown](https://www.galerne.eu/docs/migrate-markdown.md): Import a folder of Markdown or MDX files with front matter into Galerne, and export Galerne content as Markdown files: folder layout, languages, drafts, media and losses. - [Export format](https://www.galerne.eu/docs/export.md): The galerne-export/1 format, newline-delimited JSON with schema, doc, media and end lines, available on every plan, and the import lines it pairs with. ## Account - [Members, tokens and sign-in](https://www.galerne.eu/docs/members.md): How people sign in, create projects and invite members, how agents get access through OAuth or a token, what each kind of token can do, and how to export or delete your account. - [SSO and SCIM](https://www.galerne.eu/docs/sso.md): Sign in to a project with your identity provider over OIDC for a verified email domain, and provision and deactivate members with SCIM 2.0. Business plan. - [Limits and plans](https://www.galerne.eu/docs/limits.md): Plan limits per project, what counts toward them, what happens at 80% and 100%, overage prices, and limits per request. - [Billing](https://www.galerne.eu/docs/billing.md): How paid plans are bought and billed: checkout with Mollie, monthly or yearly billing, plan changes, cancelation, usage invoices, VAT for EU and other customers, and the billing routes of the API. ## Optional - [Platform](https://www.galerne.eu/platform): Every capability of Galerne in one page, each with a short example. - [Pricing](https://www.galerne.eu/pricing): Plans, limits, overage prices and the Tramontane bundle. - [Sovereignty](https://www.galerne.eu/sovereignty): Where content is stored and served, and the providers involved. - [Data processing agreement](https://www.galerne.eu/legal/dpa): Processing terms, including the agent data flow. - [Subprocessors](https://www.galerne.eu/legal/subprocessors): Companies that process data for Galerne. - [OpenAPI](https://www.galerne.eu/docs/openapi.json): The HTTP API as OpenAPI 3.1. - [Full docs](https://www.galerne.eu/llms-full.txt): Every docs page in one Markdown file.