JavaScript is off. The country switcher and the demos need it; everything else on this page works.
Open an account before 31 December 2026 and pay €1.95 instead of €2.95 per site per month, for life. The conditions
WordPress with GitHub Copilot
GitHub Copilot knows WordPress in general. It does not know your sites, your plugins or what changed an hour ago, and every question about them costs you tokens while it works that out. Connect WebCrew once and GitHub Copilot asks WebCrew, which does know. Reading is instant; every change is logged and can be undone in one click.
Free for one site. Your own AI tools connect today. No card.
GitHub Copilot is a product of GitHub. WebCrew is not affiliated with it; any MCP client connects.
| Site | Result |
|---|---|
| aldermere.org | 82 → 61unknown administrator added Sunday 02:14 |
| northlight.studio | 95 → 88Yoast SEO update waiting |
| 10 other sites | unchanged |
Nothing was changed. A change would become a draft in WebCrew that waits for your approval.
What changes for you
Every question about my sites costs tokens while the model works out what it is looking at.
Tokens pay for the answer, not for the trial and error.
I will not give a chatbot a key to a live site.
Reading is instant. Every write waits for a person.
We use three different AI tools across the team.
One connection, every site, every tool.
What you can ask
Once connected, GitHub Copilot can ask WebCrew anything your dashboard knows, and can make changes for you that show up in the log, with undo.
Scopes and what asks first, in detailFour steps
One production site is free, for as long as you like. No card.
Upload the connector plugin in wp-admin, or add WebCrew's SSH key on the server (recommended). Two ways to connect, with a guide per hosting panel.
Dashboard → Settings → AI tools shows the MCP address and creates a token with the scopes you choose. Add it in GitHub Copilot where connectors or MCP servers live.
"List the sites where the health score dropped this week and why." Reading answers at once. A change becomes a draft in WebCrew that waits for your approval.
VS Code with Copilot: add to .vscode/mcp.json: {"servers":{"webcrew":{"type":"http","url":"<address>"}}}, then start the server from the editor.
Menu names follow the tool's current release; the knowledge base keeps the exact path up to date.
Why tokens, not your tokens
WebCrew's own WordPress model knows how each plugin stores its data, how a layout is built and what your sites look like right now. New plugins and layouts are added to it every day, and GitHub Copilot uses all of it through one connection. Every account starts with 1,000 tokens a month.
Questions
It gets access to WebCrew, with the scopes you choose. Reading returns what the dashboard knows. Writing creates a draft in WebCrew; nothing reaches a site without a person approving it there.
The connection is included in Free and Standard. Questions and drafts cost tokens: 1,000 included every month, then €5 per 1,000, less from 10,000. GitHub Copilot's own subscription is separate and yours.
No. Your content is never sold and never used to train a model, by WebCrew or by a provider it uses.
Yes. The assistant inside wp-admin and your own tools over MCP share the same approval queue and the same token balance.
One of two things: the WebCrew connector plugin, uploaded in wp-admin like any plugin, or one SSH key for the site's own user. Nothing else changes on the site.
Yes. Connect your tool to WebCrew over MCP and ask about the site from your own chat. Reading is instant; changes are made for you, logged, and undone in one click.
The first site is free, for as long as you like. Every site after that is billed per site per day, monthly, for the days it was on. Plugins are never counted.
No. Your content is never sold and never used to train a model, by WebCrew or by a provider it uses.
It updates through its own licence. WebCrew shows the pending version, takes the restore point first and keeps the code difference, the same as for any other plugin.
Free for one site. No card.