agents and mcp

Plug any agent into your content

Every Galerne project runs its own MCP server. Claude, Cursor, ChatGPT or an agent you wrote connects to it, reads your content model and your writing guidelines, and edits content on a branch that a person reviews.

connect

One URL per project

The server speaks MCP over streamable HTTP. MCP clients that support OAuth open a sign-in page, where you pick the project and the agent member the client acts as. Clients without OAuth use a project token in the Authorization header.

The galerne CLI also runs the same tools locally over stdio with galerne mcp.

connect Claude, Cursor or ChatGPT →
# the MCP server of the project "acme"
https://api.galerne.cloud/p/acme/mcp

# Claude Code
claude mcp add --transport http acme https://api.galerne.cloud/p/acme/mcp

# Cursor: .cursor/mcp.json
{ "mcpServers": { "acme": { "url": "https://api.galerne.cloud/p/acme/mcp" } } }
  • transportStreamable HTTP, or stdio through the CLI
  • sign-inOAuth 2.1 with PKCE and dynamic client registration, or a gal_ token
  • accessEach connection acts as one agent member, with its own role and rules
tools

79 tools that know your schema

Every operation in Galerne is one tool, shared by the MCP server, the HTTP API, the CLI and the studio. Writes run the same validation everywhere, and errors name the field path and the rule so the agent can fix its input.

read
  • get_schemaThe content model: document types, fields (as JSON Schema), blocks and languages.
  • get_guidelinesThe project's voice, audience, glossary, banned words and rules.
  • queryFind documents with a JSON filter.
  • get_docOne document with its current values (rich text as Markdown), status, revision and studio link.
  • list_docsDocuments of a type (or all), most recently changed first, with status and last author.
  • searchFull text search over titles and text fields.
  • get_historyWho changed a document and when (people and agents).
  • list_branchesContent branches with their status (open, in_review, approved, merged) and number of changed docs.
  • get_referencesDocuments that reference this one ("used by"), and the documents it references.
  • checkValidation and content checks (broken references and links, missing alt text, heading order, missing or outdated translations, duplicates) for one doc, a type, or a whole branch.
  • list_mediaMedia library with search, tag and type filters; unused=true finds files no doc uses.
  • get_mediaOne media file: details, URL and the docs that use it.
  • branch_changesWhat a branch changes: docs created, edited or deleted, field-level diffs, conflicts with main, validation errors, the schema deployed on the branch (what promotion deploys on main), review events and content checks.
  • list_commentsComments and tasks on a doc or branch.
  • list_schedulesLists the pending scheduled publishes, unpublishes and releases, soonest first.
  • propose_schema_changeChecks a full schema config (galerne.config.ts as JSON) against the one deployed on main and returns the diff and problems.
  • get_audit_logWho (person, agent or token) did what on this project, newest first.
  • accessibility_reportAccessibility issues in content (European Accessibility Act): images without alt text, skipped heading levels, vague link text.
  • get_cache_settingsPer type: how long sites cache answers that depend on it (life: seconds, minutes, hours, days, weeks, max), and which other types a publish of it also purges (purges).
  • export_toWrites a branch in another CMS format (schema, content, assets): sanity, contentful, storyblok, wordpress, payload, markdown, or galerne (the plain export).
  • get_analyticsPage views of a published doc over the last 30 days (site analytics), per day, with the trend of the last 7 days against the 7 before.
  • list_filesFiles of the site repo on a branch, optionally under a folder.
  • read_fileOne file of the site repo on a branch: text as UTF-8, other files as base64 (1 MB at most).
  • code_branchesBranches of the site repo with their last commit, the content branch of the same name, and the preview URL when built.
  • code_changesCommits and files a branch changes compared to main: what a review of the branch covers on the code side.
  • build_statusLatest builds of the site on Tramontane, for one branch or all.
  • build_logsLog lines of one build, by page: pass `next` back as `after` until it is null.
  • preview_urlWhere to see a branch: its own build when its code changed (code and content of the branch), else the production site in draft mode on that content branch.
  • list_mirrorsWhere the site repo is mirrored, with the last push and its error if any.
  • list_componentsLists the site's components from its design manifest: atoms, components and blocks, with their props, controls, variants and, for blocks, the CMS fields.
  • site_analyticsVisitors and page views of the managed site in production over a range (24h, 7d, 30d, 90d), with the range before it, and the top pages, routes, referrers, countries, devices, browsers and custom events.
  • list_sourcesExternal APIs that fill docs: their type, schedule, target and last run.
  • source_runsThe run log: counts (created, updated, unchanged, removed, failed), errors per item, duration.
  • get_sourceOne source with its mapping, secret names (values are never returned) and recent runs.
write
  • create_branchA branch for a unit of work ("translate to German", "alt text pass").
  • create_docCreates a document on a branch.
  • patch_docChanges fields by path: set { "title": "…", "seo.description": "…", "body": "Markdown…", "content[<key>].heading": "…", "role.fr": "…" }, unset ["path"], insert items into lists.
  • publish_docMakes the current draft the published version on this branch.
  • unpublish_docRemoves the published version; the draft stays.
  • delete_docDeletes a document on a branch.
  • restore_versionRestores a past version (seq from get_history), whole or only some field paths, as a new change.
  • upload_mediaAdds an image or file from a public https URL or base64 data.
  • update_mediaSets alt text, title, caption, credits, license, tags or expiry of a media file.
  • update_from_mainBrings changes made on main since the branch started into the branch.
  • close_branchCloses a branch without promoting it.
  • schedulePublishes or unpublishes a doc at a time (ISO 8601 with offset).
  • cancel_scheduleCancels a pending scheduled publish or unpublish.
  • update_branchChanges a branch title or description, or makes it a release with a publish time (publishAt null removes the time).
  • rollback_promotionPuts the docs a promotion (or release) changed on main back to their state before it, as new changes.
  • delete_mediaDeletes a media file.
  • replace_mediaReplaces the bytes of a media file in place: same id, so every doc using it shows the new file.
  • import_fromCopies content from Sanity, Contentful, Storyblok, WordPress, Payload or Markdown files into a branch (default import/<cms>-<date>): schema inferred, docs with references, rich text, translations, drafts and assets, ids kept.
  • write_filesCreates, updates or deletes files of the site repo in one commit on a branch (created from main when new, with the content branch of the same name).
  • git_accessCredentials to clone the site repo and push branches with plain git (for agents with a shell).
  • update_themeChanges design tokens in theme/tokens.json on a branch, in one commit.
  • sync_sourceFetches the API and writes the changes now: new and changed items, removed items unpublished.
  • set_overrideKeeps the current values of fields a data source owns: syncs stop writing them.
  • reset_overrideThe source owns these fields again (all overridden ones without paths).
review
  • request_reviewAsks people to review a branch.
  • approveApproves a branch under review, or asks for changes with a note.
  • commentComments on a doc (optionally a field path) or a branch.
  • promoteMerges a branch into main (text merges by character; fields both sides changed are conflicts).
  • update_commentEdits your comment, resolves or reopens a thread, marks a task done, or changes its assignee or due date.
  • delete_commentDeletes a comment and its replies.
  • request_code_reviewAsks people to review a branch: its code changes (compared to main) and its content changes, together under one name.
  • promote_codeMerges a code branch into main (a merge commit); Tramontane then rebuilds production.
schema
  • deploy_schemaDeploys a schema config.
  • set_cache_settingsSets the cache settings of some types (expert mode).
  • create_siteCreates the project's site: a git repo from a template on Galerne's Forgejo, a site on Tramontane (EU hosting) built from it, its environment (API URL, project, read and preview tokens, preview and webhook secrets) and the revalidation webhook.
  • delete_siteDeletes the project's managed site: the hosted site on Tramontane, the git repo and its mirrors settings, git access, the site's tokens and its revalidation webhook.
  • refresh_siteReads the hosted site again, stores its URL, wires the revalidation webhook once the URL is known (then rebuilds production), and gives the site the current API URL and preview secrets again (after a rotation; branch builds get their own secret and draft token if they have none yet).
  • set_mirrorCopies the site repo to your own GitHub or GitLab repository on every change (a push mirror).
  • update_site_settingsWhere content is published: the public site URL, the path pattern per type (routes, e.g.
  • site_envReturns a .env.local for running the site on your machine: API URL, project, studio URL, the preview secret and a new read token made for it (shown once; revoke it in settings, API tokens).
  • set_site_analyticsTurns web analytics of the managed site on or off.
  • create_sourceAdds an external API that fills docs of one type.
  • update_sourceChanges a source: its definition (studio sources only; config sources change in galerne.config.ts), secrets (null removes one), enabled, or a new hook secret.
  • delete_sourceRemoves a studio source and its run log.
  • test_sourceDry run: fetches the API and maps the first items with a saved source or a draft definition.
every tool with its inputs →
branches and review

Agents propose, people promote

A branch holds a unit of work. Documents read through to main until the branch changes them, so an agent sees live content while it works. When it is done, a person reviews the branch in the studio and promotes it.

branches, merges and conflicts →
  1. create_branchThe agent opens a branch such as agent/translate-de.
  2. create_doc, patch_doc, upload_mediaIt writes by field path, with rich text as Markdown. Passing the revision it read protects edits made in the meantime.
  3. checkIt runs the content checks on the branch and fixes what they report.
  4. request_reviewIt asks for review with a note on what it changed and why.
  5. approve and promoteA person reads the field diff and the checks, comments or approves, then promotes the branch to main, optionally publishing it. Agents cannot approve.
agent members

Each agent is a member with its own rules

You create an agent in the project settings, or the OAuth sign-in creates one for you. Agents never count as seats: the Free plan includes 2 agents and paid plans include as many as you need. Their MCP and API calls are metered like any other.

  • ownerThe person responsible for the agent
  • roleContributor by default: read, write on branches, upload media, comment and ask for review
  • branchesPatterns the agent may write on, such as agent/*
  • typesDocument types the agent may write, such as post and page
  • mainWriting on main is off until you allow it
  • promoteOff until you allow it; most agents ask for review instead
  • rate limit120 requests per minute by default, set per agent
  • kill switchDisabling an agent stops all its tokens at once
guidelines and prompts

Every agent writes in your voice

Every project has a Guidelines document, filled in the studio and served by get_guidelines. Agents read it before they write, so a translation agent and an SEO agent use the same terms.

The MCP server also ships three prompts. Your MCP client lists them, and your agent runs them with its own model.

  • voiceVoice and tone, as rich text
  • audienceWho the content is for
  • glossaryTerms and the wording to use, per language
  • banned wordsWords agents must avoid
  • rules and examplesHouse rules, and good examples to follow
  • translate_docTranslates a document into another language on a branch, using the glossary
  • alt_textFinds images without alt text and writes it
  • seo_passReviews titles, descriptions and headings of a document type
data flow

We run no language model

Galerne hosts your content and the tools. The model belongs to your agent: Claude, Mistral, GPT or one you run yourself. When an agent calls a tool, Galerne sends the result to the MCP client, and the client passes it to the model you chose. That transfer is between you and your model provider, under your contract with them.

The tokens page of each project lists every agent and OAuth client with access, when each was last used, and a button to revoke it. The DPA states the same flow.