{"id":7,"date":"2026-08-19T02:46:05","date_gmt":"2026-08-19T02:46:05","guid":{"rendered":"https:\/\/hycpxbxyuf.wordifysites.com\/?page_id=7"},"modified":"2026-08-19T04:10:26","modified_gmt":"2026-08-19T04:10:26","slug":"wordify-mcp","status":"publish","type":"page","link":"https:\/\/hycpxbxyuf.wordifysites.com\/","title":{"rendered":"Wordify MCP"},"content":{"rendered":"\n
\n

Model Context Protocol<\/p>\n\n\n\n

Run your WordPress hosting by asking for it<\/h1>\n\n\n\n

The Wordify MCP server connects Claude, ChatGPT, and other AI assistants directly to your hosting account. Ask a question in plain language, and your assistant calls the real Wordify API \u2014 listing sites, clearing caches, provisioning servers, reading debug logs \u2014 and reports back. No API keys. No dashboards to click through.<\/p>\n\n\n\n

Your MCP server URL<\/p>\n\n\n\n

https:\/\/console.wordify.com\/mcp<\/code><\/pre>\n\n\n\n
That single URL is the entire configuration. 48 tools<\/strong>, one OAuth sign-in, about a minute to set up.<\/p>\n<\/div>\n\n\n\n
\n
What is MCP, and why should you care?<\/h2>\n\n\n\n
The Model Context Protocol<\/strong> is an open standard for giving AI assistants structured access to real systems. Instead of an assistant guessing at HTTP endpoints or asking you to paste screenshots, it gets a typed catalogue of actions it can take \u2014 each with documented parameters, validation, and error handling.<\/p>\n\n\n\n
Wordify’s MCP server exposes the same \/api\/v1\/*<\/code> surface the console itself uses. That matters more than it sounds: your assistant isn’t working against a simplified or second-class API. It sees the same sites, the same config sections, the same task queue, and the same permission model you do.<\/p>\n\n\n\n
\n
\n
Without MCP<\/p>\n\n\n\n
Open the console. Find the site. Click into settings. Repeat for the other eleven sites. Realise you forgot which ones you already did.<\/p>\n<\/div>\n\n\n\n
\n
With MCP<\/p>\n\n\n\n
“Which of my sites are on an end-of-life PHP version, and what would upgrading them break?” \u2014 one question, one answer, every site covered.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
Connect in about a minute<\/h2>\n\n\n\n
Connecting is a one-click OAuth flow: paste the server URL into your assistant, sign in to Wordify to authorise, done. There are no API keys to mint, no tokens to paste, and no config files to edit.<\/strong><\/p>\n\n\n\n
In the console, everything below is built into Integrations \u2192 AI Connectors<\/strong> \u2014 your server URL with a copy button, per-client instructions, and a live list of authorised assistants.<\/p>\n\n\n\n
Claude<\/h3>\n\n\n\n
    \n
  1. Open Settings \u2192 Connectors<\/strong> and choose Add custom connector<\/strong>.<\/li>\n\n\n\n
  2. Paste https:\/\/console.wordify.com\/mcp<\/code> into Remote MCP server URL<\/strong>, then click Add<\/strong>.<\/li>\n\n\n\n
  3. Click Connect<\/strong> and sign in to Wordify to authorise. Claude registers itself and obtains its own OAuth token behind the scenes.<\/li>\n<\/ol>\n\n\n\n
    Custom connectors require Claude Pro or Max. On Team or Enterprise plans, an organisation owner adds the connector before members can use it.<\/p>\n\n\n\n
    ChatGPT<\/h3>\n\n\n\n
      \n
    1. Open Settings \u2192 Connectors \u2192 Advanced<\/strong> and turn on Developer mode<\/strong>.<\/li>\n\n\n\n
    2. Go to Settings \u2192 Connectors \u2192 Create<\/strong>.<\/li>\n\n\n\n
    3. Paste the server URL into Connector URL<\/strong>, save, and authorise by signing in to Wordify.<\/li>\n<\/ol>\n<\/div>\n\n\n\n
      \n
      Your first five minutes<\/h2>\n\n\n\n
      Start a new conversation and just ask. You don’t need to name tools or learn a syntax \u2014 the tool descriptions tell your assistant how each one is used.<\/p>\n\n\n\n
      Ask this<\/th>Tools it will reach for<\/th><\/tr><\/thead>
      “List my Wordify sites and tell me which are on an older WP version.”<\/td>list_sites<\/code><\/td><\/tr>
      “Clear the cache on all my sites.”<\/td>dispatch_task<\/code> \u2192 get_task<\/code><\/td><\/tr>
      “Is anything wrong across my fleet right now?”<\/td>audit_sites<\/code><\/td><\/tr>
      “Preview what upgrading every site to the latest WordPress would do.”<\/td>dispatch_task<\/code> with dry_run=true<\/code><\/td><\/tr>
      “My site is throwing a 500 \u2014 what’s in the error log?”<\/td>update_site_config<\/code> \u2192 get_debug_log<\/code><\/td><\/tr>
      “Spin up a staging copy of example.com so I can test the plugin update.”<\/td>create_staging<\/code> \u2192 get_task<\/code><\/td><\/tr>
      “What did my team spend last month?”<\/td>get_usage<\/code> \/ list_invoices<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      MCP sessions automatically get a 5\u00d7 rate-limit bucket \u2014 300 requests\/min versus the public API’s 60\/min \u2014 to accommodate the chattier call pattern of an assistant working through a conversation. No opt-in needed.<\/p>\n<\/div>\n\n\n\n
      \n
      What’s in the box: 48 tools<\/h2>\n\n\n\n
      The surface covers the full lifecycle of a WordPress site \u2014 from provisioning one to billing for it. You never call these by name; they’re what your assistant picks from.<\/p>\n\n\n\n
      Group<\/th>Tools<\/th><\/tr><\/thead>
      Orientation<\/strong><\/td>get_me<\/code>, list_teams<\/code>, select_team<\/code><\/td><\/tr>
      Sites<\/strong><\/td>list_sites<\/code>, get_site<\/code>, list_plans<\/code>, provision_site<\/code>, audit_sites<\/code>, clear_site_cache<\/code>, enable_site_cdn<\/code>, disable_site_cdn<\/code><\/td><\/tr>
      Configuration<\/strong><\/td>update_site_config<\/code> \u2014 one tool, a section<\/code> discriminator for PHP, cache, CDN, Redis, WordPress settings, basic auth, and debug flags<\/td><\/tr>
      Cron<\/strong><\/td>get_site_cron<\/code>, update_site_cron<\/code><\/td><\/tr>
      Debugging<\/strong><\/td>get_debug_log<\/code><\/td><\/tr>
      Admin access<\/strong><\/td>get_admin_login_link<\/code>, list_wp_users<\/code><\/td><\/tr>
      WP-CLI<\/strong><\/td>run_wp_cli<\/code><\/td><\/tr>
      Plugins & themes<\/strong><\/td>list_plugins<\/code>, install_plugin<\/code>, toggle_plugin<\/code>, list_themes<\/code><\/td><\/tr>
      Content<\/strong><\/td>list_posts<\/code>, get_post<\/code>, create_post<\/code>, update_post<\/code><\/td><\/tr>
      Backups<\/strong><\/td>list_backups<\/code>, create_backup<\/code>, restore_backup<\/code><\/td><\/tr>
      Staging<\/strong><\/td>create_staging<\/code>, push_staging<\/code>, pull_staging<\/code><\/td><\/tr>
      Cloning<\/strong><\/td>clone_site<\/code><\/td><\/tr>
      Domains<\/strong><\/td>list_domains<\/code>, add_domain<\/code>, recheck_domain_dns<\/code><\/td><\/tr>
      Bulk tasks<\/strong><\/td>dispatch_task<\/code>, get_task<\/code>, list_tasks<\/code><\/td><\/tr>
      Billing (read-only)<\/strong><\/td>list_invoices<\/code>, get_usage<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Seven older per-section tools (update_php<\/code>, update_cache<\/code>, update_cdn<\/code>, update_redis<\/code>, update_wordpress_settings<\/code>, update_basic_auth<\/code>, update_debug_mode<\/code>) remain registered as deprecated aliases of update_site_config<\/code> so existing agents keep working. Some tools \u2014 the content and WP-CLI ones \u2014 are feature-gated and only appear for teams entitled to them.<\/p>\n<\/div>\n\n\n\n
      \n
      Five concepts that make it click<\/h2>\n\n\n\n
      1. Your team decides what you can do<\/h3>\n\n\n\n
      OAuth proves who<\/em> you are. What you’re allowed to do<\/em> is decided by your team role \u2014 the same check the web console applies. So if a management action fails, it means your role lacks that capability, not that a token is missing a scope. If you belong to several teams, your assistant calls select_team<\/code> once to set the active one; single-team users skip it entirely.<\/p>\n\n\n\n
      2. Slow things return a receipt, not a result<\/h3>\n\n\n\n
      Provisioning a site, creating a backup, enabling a CDN \u2014 these take minutes, so they return a task handle<\/strong> immediately rather than blocking. Your assistant polls it with get_task<\/code> and reports progress as it goes. A brand-new site moves through six steps: DNS record, server account, WordPress install, plugins, configuration, SSL certificate.<\/p>\n\n\n\n
      3. Ask once, apply everywhere<\/h3>\n\n\n\n
      dispatch_task<\/code> fans a single action across up to 100 sites<\/strong> in one call. “Clear the cache on all my sites” should produce one call, not one per site. For anything destructive or wide-blast, dry_run=true<\/code> shows you what would<\/em> happen first. And audit_sites<\/code> answers “what’s wrong across my fleet?” in a single request rather than a per-site loop.<\/p>\n\n\n\n
      4. Destructive actions are fenced off by default<\/h3>\n\n\n\n
      The run_wp_cli<\/code> escape hatch runs raw WP-CLI for the long tail no purpose-built tool covers. It ships two guardrails. Some commands are blocked outright<\/strong> and cannot be run at all \u2014 db<\/code>, config<\/code> (it would expose database passwords and secret keys), eval<\/code>, shell<\/code>, server<\/code>, package<\/code>, and cli<\/code>. Others \u2014 deletes, non-dry-run search-replace, cache flushes \u2014 are refused while safe mode is on<\/strong>, which is the default. Turning safe mode off is a deliberate act, and every run is recorded in the site’s activity log either way.<\/p>\n\n\n\n
      5. Nothing gets published behind your back<\/h3>\n\n\n\n
      The content tools are draft-first by design: create_post<\/code> saves a draft unless you explicitly ask for status=\"publish\"<\/code>. Publishing is never implicit. Edits create a WordPress revision, so they’re always reversible, and update_post<\/code>‘s trash action moves content to the trash rather than permanently deleting it.<\/p>\n<\/div>\n\n\n\n
      \n
      When something goes wrong<\/h2>\n\n\n\n
      Failures come back as a structured error with a stable code<\/code>, a human-readable message, and a request ID you can quote to support.<\/p>\n\n\n\n
      Code<\/th>What it means<\/th>What to do<\/th><\/tr><\/thead>
      unauthenticated<\/code><\/td>The connector isn’t authorised \u2014 token expired or disconnected<\/td>Re-authorise from your assistant<\/td><\/tr>
      insufficient_ability<\/code><\/td>Your team role can’t manage sites<\/td>Ask a team owner to upgrade your role<\/td><\/tr>
      insufficient_capability<\/code><\/td>Your role lacks permission for this specific action<\/td>Ask a team owner to escalate your role<\/td><\/tr>
      team_not_accessible<\/code><\/td>No team could be resolved<\/td>Select a team first, or contact support<\/td><\/tr>
      validation_failed<\/code><\/td>Bad input<\/td>The error names the offending field<\/td><\/tr>
      not_found<\/code><\/td>It doesn’t exist \u2014 or<\/em> it isn’t in your current team<\/td>Check the ID and which team is active<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      One genuinely useful debugging habit: an empty debug log is ambiguous unless you know whether logging was on. get_debug_log<\/code> returns the WP_DEBUG flag state alongside the log tail, so “nothing here” and “logging was off” are never confused.<\/p>\n<\/div>\n\n\n\n
      \n
      You stay in control<\/h2>\n\n\n\n
      Every assistant you authorise appears under Connected AI clients<\/strong> in Integrations \u2192 AI Connectors, showing when it connected and when its access expires. Click Disconnect<\/strong> on anything you no longer use \u2014 or don’t recognise \u2014 and it loses access immediately. You can reconnect any time by authorising again.<\/p>\n\n\n\n
      A few things deliberately stay in the web console rather than the MCP surface: payment changes, invoice PDF downloads, deleting a domain, changing a site’s primary domain, suspending a site, and deleting a site. Those are one-way doors, and they should be clicked on purpose.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
      How to connect an AI assistant to your Wordify hosting with the Model Context Protocol \u2014 setup, the 48 tools, and the concepts that make it click.<\/p>\n","protected":false},"author":0,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-no-title","meta":{"footnotes":""},"class_list":["post-7","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=\/wp\/v2\/pages\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7"}],"version-history":[{"count":4,"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=\/wp\/v2\/pages\/7\/revisions"}],"predecessor-version":[{"id":20,"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=\/wp\/v2\/pages\/7\/revisions\/20"}],"wp:attachment":[{"href":"https:\/\/hycpxbxyuf.wordifysites.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}