Integrations
Plugged into what you already use.
Your host rebuilds when something goes live. Your repository gets every save. Your bucket holds the files, your video host the films, and your agents get every command as a tool. Here’s each one, where it runs, and how it’s set up.
a deploy hook
{
"name": "Rebuild the client site",
"url": "https://api.netlify.com/build_hooks/…",
"kind": "deploy",
"batchSeconds": 30
}The board
What it plugs into
Pick what you need it for. Each tile says where it runs: on Moteur Cloud, on a server you run, or both.
VercelBoth
Rebuilds the site when something goes live, once for changes close together.
How it’s set up: Setup › Webhooks › Rebuild the site, with the host’s deploy hook
NetlifyBoth
Rebuilds the site when something goes live, once for changes close together.
How it’s set up: Setup › Webhooks › Rebuild the site, with the host’s deploy hook
Cloudflare PagesBoth
Rebuilds the site when something goes live, once for changes close together.
How it’s set up: Setup › Webhooks › Rebuild the site, with the host’s deploy hook
Your own serverBoth
A signed message on each event you choose, retried for two hours if it’s down.
How it’s set up: Setup › Webhooks: events, filters, headers
GitHubBoth
Every save is pushed to the repository, as a commit with its author’s name.
How it’s set up: Setup › Project › Git, and a token for a private repository
GitLabBoth
Every save is pushed to the repository, as a commit with its author’s name.
How it’s set up: Setup › Project › Git, and a token for a private repository
BitbucketBoth
Every save is pushed to the repository, as a commit with its author’s name.
How it’s set up: Setup › Project › Git, and a token for a private repository (user name x-token-auth)
Amazon S3Moteur Cloud
The project’s files in your bucket, and every one moved there in one go.
How it’s set up: Setup › Media › Storage: bucket, region, keys
Cloudflare R2Moteur Cloud
The project’s files in your bucket, and every one moved there in one go.
How it’s set up: Setup › Media › Storage: account, bucket, keys
MuxMoteur Cloud
Videos uploaded to your Mux account, played from its player.
How it’s set up: Setup › Media › Videos
VimeoMoteur Cloud
Videos uploaded to your Vimeo account.
How it’s set up: Setup › Media › Videos
Cloudflare StreamMoteur Cloud
Videos uploaded to your Stream account.
How it’s set up: Setup › Media › Videos
YouTubeMoteur Cloud
Videos uploaded to your channel.
How it’s set up: Setup › Media › Videos
Claude CodeBoth
Every Moteur command as a tool, with a person approving what goes live.
How it’s set up: claude mcp add --transport http moteur https://api.moteur.io/mcp
CodexBoth
Every Moteur command as a tool, with a person approving what goes live.
How it’s set up: codex mcp add moteur --url https://api.moteur.io/mcp
Any MCP clientBoth
Claude Desktop and others, through the local server and your CLI sign-in.
How it’s set up: npx -y @moteurio/mcp
OpenAI, Google or falMoteur Cloud
Pictures made from a description, for the image helper.
How it’s set up: Setup › AI › Pictures from a description
ElevenLabs or falMoteur Cloud
An article read aloud, for the audio helper.
How it’s set up: Setup › AI › Speech from text
Meshy or falMoteur Cloud
A 3D model from a description.
How it’s set up: Setup › AI › 3D models from a description
GitHub, Google, Microsoft, OIDCYour server
Sign in with an account people already have, for everyone on the server.
How it’s set up: MOTEUR_HOST_PLUGINS=@moteurio/plugin-auth-google, and its client id and secret
Email (SMTP)Both
Invitations, sign-up codes, review requests and form letters, by email.
How it’s set up: SMTP_HOST, SMTP_FROM on your server. On Moteur Cloud, we send them
MapsBoth
Places, areas and routes as fields, drawn with your own map library.
How it’s set up: geo/location, geo/area and geo/polyline fields. Leaflet or MapLibre on the site
EmbedsBoth
A link to a video or a song becomes the player, in a block.
How it’s set up: YouTube, Vimeo, Spotify… through noembed.com
Storage, video hosts and the AI helpers are Moteur Cloud’s own plugins. Sign-in providers are set up by whoever runs the server.
Up close
The three you’ll use first
For a client site, these do most of the work.
Build
A deploy hook
Paste the build hook from Vercel, Netlify or Cloudflare Pages. When something goes live, Moteur waits half a minute for the rest, then starts one build.
- Entries, pages, menus, redirects, files
- Signed, and retried if the host is down
Setup › Webhooks › Rebuild the site
{ "name": "Rebuild the client site", "url": "https://api.netlify.com/build_hooks/…", "kind": "deploy", "batchSeconds": 30 }Git
The client’s own repository
Every save is a commit, pushed to the address you give. For a private repository, a token that can write to it, kept encrypted.
- https, with no password in the address
- The Studio says when a push didn’t arrive
GET /projects/client-site/git/status
{ "branch": "main", "remoteUrl": "https://github.com/your-agency/client-site.git", "lastCommit": { "hash": "4f1c2e9", "message": "Publish article/spring-menu — Louise Gagnon", "authorName": "Louise Gagnon", "date": "2026-10-26T14:02:11Z" }, "unpushed": 0 }Agents
MCP
Claude Code, Codex and any MCP client get every Moteur command as a tool, for the projects you choose.
- A person approves what goes live
- Read-only, content or full setup
terminal
# Hosted: sign in in the browser, choose the projects claude mcp add --transport http moteur https://api.moteur.io/mcp # Or local, through the CLI's sign-in npm install -g @moteurio/cli && moteur auth login claude mcp add moteur -- npx -y @moteurio/mcp
Questions about integrations
An agency developer asksCan a visitor search the site through Moteur?
MoteurNot yet. Build your site’s search index from the published pages, with a tool like Pagefind. Search on Moteur’s side, through Algolia or Meilisearch, isn’t ready to offer.
An agency owner asksDo you connect to Shopify?
MoteurNot as a feature yet. There’s a first piece: pulling products in as entries, through the API. It has no Studio screen, so we don’t count it here.
An agency owner asksCan our team sign in with Google or Microsoft on Moteur Cloud?
MoteurTalk to us. The sign-in plugins exist for GitHub, Google, Microsoft and any OIDC provider. On a server you run, you switch them on yourself. Anyone can add two-step sign-in either way.
A developer asksWhat if ours isn’t on the board?
MoteurA signed webhook reaches anything with an address, and the plugin SDK adds fields, blocks, storage and sign-in providers. Read a real plugin on the Plugins page.
A self-hoster asksWhy are storage and video Moteur Cloud only?
MoteurThey’re Moteur Cloud’s own plugins, kept apart from the open-source engine. On your own server, files stay on its disk unless you write a storage plugin.
Plug in your first project.
Start for free, paste a deploy hook, and publish something.