JavaScript is off. The country switcher and the demos need it; everything else on this page works.

WebCrew
Start free

Your own AI tools

Use WordPress with the AI tool you already have, the right way

You already pay for Claude, ChatGPT or Cursor. Connect WebCrew to it once and ask about every site you look after from the tool you already use. Reading is instant; every change is logged and can be undone in one click.

Start free How the MCP server works

Included in Free and Standard. No card.

ChatGPTNew chatSearch chatsLibraryGPTsYour sites (WebCrew)
ChatGPT WebCrew connector
Show me every site with an update waiting and what each update changes.
asked WebCrew · read only · 3 tokensHere is what WebCrew has for your 12 sites:
SiteResult
harbourview.nlWooCommerce 10.2.1fixes tax rounding at checkout
northlight.studioYoast SEO 26.4schema output changes
aldermere.orgACF 6.5.2security fix; approve today

Nothing was changed. A change would become a draft in WebCrew that waits for your approval.

Ask about your sites…

Pick your tool

Pick the tool you already use. Its page shows where WebCrew goes and what to ask first.

Claudemanage WordPress from ClaudeChatGPTmanage WordPress from ChatGPTCursormanage WordPress sites from CursorGitHub CopilotWordPress site management in CopilotGeminimanage WordPress from GeminiPerplexityask Perplexity about your WordPress sitesLe Chat (Mistral)manage WordPress from Le ChatWindsurfmanage WordPress sites from WindsurfRaycastcheck your WordPress sites from RaycastJetBrains IDEsmanage WordPress from PhpStormVS Codemanage WordPress sites from VS Coden8nautomate WordPress site management with n8n

Product names belong to their owners. Any MCP client connects; these are the ones we test with.

What changes for you

Three situations, minute by minute, once your tool is connected

Every question about my sites costs tokens while the model works out what it is looking at.

  • You ask in your AI tool: which sites still run PHP 8.1?
  • your AI tool asks WebCrew, which already knows every site, version and finding.
  • The answer, per site, with the action. A few tokens, no token trail.

Tokens pay for the answer, not for the trial and error.

I will not give a chatbot a key to a live site.

  • You ask your AI tool to fill in the missing meta descriptions on a client site.
  • WebCrew turns it into a draft: one line per page, restore point first.
  • You read the difference and approve, or decline. Nothing touched the site before that.

Reading is instant. Every write waits for a person.

We use three different AI tools across the team.

  • One MCP server, one token per person, with the scopes you choose.
  • The same log and undo, whichever tool asks.
  • Revoke a token in the dashboard and that tool is out; the others keep working.

One connection, every site, every tool.

Connect one site. Ask from the tool you already have.

Start free How to connect a site
Start free