WordPress.org

Plugin Directory

My Site Hand – AI Assistant, Site Health & MCP Server for WordPress

My Site Hand – AI Assistant, Site Health & MCP Server for WordPress

Сүрөттөө

My Site Hand finds what is wrong with your WordPress site, and helps you fix it.

Activate the plugin and it scans your site straight away. No token, no API key, no Node.js, no terminal. About thirty seconds later you get a health score out of 100 and a list of real problems on your own site — and you can repair most of them inline, right there in the report.

🔍 The Site Health Scan (no setup required)

Twelve checks, run one at a time so nothing times out.

  • Broken links — checks the links in your recent posts and pages, and reports only the ones that are genuinely gone. Anything ambiguous is left alone rather than reported as a false alarm.
  • Missing alt text — images your visitors using screen readers cannot see, and search engines cannot read.
  • Missing meta descriptions — published posts and pages with no SEO description, for Yoast SEO and RankMath.
  • Oversized media — files big enough to slow your pages down, with the space you would get back.
  • Orphaned files — uploads that nothing on your site appears to use.
  • Plugin and core health — pending updates, an unsupported PHP version, missing HTTPS, errors visible to visitors, a stalled cron.
  • Images missing dimensions — the cause of pages that jump around while they load, which Google measures as a Core Web Vital.
  • Images missing lazy loading — pictures further down a post that something has opted out, so visitors download them before they are ever seen.
  • Exposed WordPress files — readme.html, license.txt and a debug log left publicly readable. The first hands an attacker your exact version; the last can contain server paths and credentials.
  • XML-RPC — reported as a notice, with the tradeoff stated plainly. It is a brute-force vector, but the WordPress mobile app and Jetpack need it, so this is only worth turning off if you use neither. Sites running Jetpack are skipped entirely.
  • Thin content — published pages with very few words. Read with judgement: a contact page is supposed to be short, and pages built from a shortcode, gallery or embed are left out.
  • Accessibility basics — links that announce nothing to a screen reader, “click here” links, more than one main heading, and headings that skip a level. Structural checks only; it does not claim to be a full audit.

⚡ Quick Fix

A list of complaints is not much use on its own. Write alt text straight into the report, replace a dead link, or trash a file you no longer need — one row at a time, with the score climbing as you go. No AI and no API key required for any of it.

Your score is kept over time, so you can watch the site improve, and you can have a short report emailed to you when something changes.

📤 Send the report to someone else

A report is more useful when the person who needs to act on it can read it.

  • PDF — opens a clean, printable page and your browser’s own print dialog. Choose “Save as PDF”. No bloated PDF library bundled into the plugin to do a job your browser already does well.
  • CSV — every issue as a row: check, severity, issue, context, link and object ID. Opens correctly in Excel and Google Sheets, in any language.
  • A shareable link — a public web page your client can open without a login, with an expiry you choose: 7, 30 or 90 days. There is no never-expires option.

Shared reports are redacted on purpose. They show the score, each check by name, and how many issues it found. They never show file names, page addresses, server paths, post or media IDs, edit links, or your plugin, theme, PHP and WordPress versions — and the two security checks are left out entirely, because publishing those would be publishing a vulnerability report about your own server. The page tells you exactly what a recipient will and will not see before you create the link, every link can be revoked instantly, and the report is a snapshot: re-scanning your site never changes what you already sent.

🤖 And when you want an AI to do the work

Everything above works on its own. Connecting an AI assistant is the optional upgrade.

Built on the open standard Model Context Protocol (MCP) developed by Anthropic (the creators of Claude), this plugin securely exposes safely-gated capabilities (Abilities) to clients like Claude Desktop, Cursor, and VS Code, so they can work on your site using plain language.

🚀 What an AI assistant can do for you:

  • Write & Edit Content – Ask Claude to draft, edit, format, or publish posts and pages directly on your site.
  • AI-Driven SEO Audits – Let your AI scan Yoast or RankMath metadata, optimize it for targeted keywords, and update titles/descriptions instantly.
  • WooCommerce Store Management – Ask your AI to list low-stock items, draft product listings, check recent orders, or summarize sales analytics.
  • Site Health & Diagnostics – Let the AI inspect PHP error logs, check loopback status, or look up site details to debug issues.
  • Zero-Config Automated Setup – No manual editing of hidden JSON config files. Copy a single command from your WordPress dashboard, paste it into your terminal, and Claude connects automatically!
  • Total Safety & Security – All tokens are SHA-256 hashed. You can toggle specific abilities (like writing or deleting) on/off with simple switches, and monitor everything the AI does in real-time with the built-in Audit Log.

📦 Included Modules:

  1. Content — posts, pages and custom post types (9 abilities)
  2. SEO — analysis and meta management, for Yoast SEO and RankMath (6)
  3. Diagnostics — site health, error logs, cron and database details (7)
  4. Media — the media library, including alt text (6)
  5. Users — accounts and roles (5)
  6. WooCommerce — products, orders and coupons (12, registers only when WooCommerce is active)

That is 33 abilities on a standard install, or 45 with WooCommerce. Every one of them is an individual switch, and a token can only call what you allow.

🔒 Security

  • API tokens are SHA-256 hashed — the raw token is shown once and never stored.
  • Every token is scoped to specific abilities. A token can only do what you explicitly allow.
  • Optional IP allowlist restricts a token to specific addresses or CIDR ranges.
  • Tokens are sent via the Authorization header, never in the URL.
  • Every action is written to a searchable audit log with configurable retention.

⚠️ Important Requirements (Honest & Transparent):

The Site Health scan and Quick Fix need none of the following. They apply only if you choose to connect an AI assistant:

  • Node.js: The automated desktop bridge (mcp-remote) requires Node.js installed on your local computer to run.
  • SSL/HTTPS: For security, your site must run on HTTPS so your API tokens remain encrypted in transit.
  • Administrator Access: You must be an administrator to generate API tokens and toggle module permissions.

External Services

Link Checker (SEO Module)

When the check-broken-links ability is called via the MCP API, this plugin sends HTTP HEAD requests to URLs found in your post content to verify they are reachable. No personal user data is transmitted — only a standard HTTP request is made to each URL being checked. This is triggered only when explicitly called by an authorized API token holder.

Link Checker (Site Health scan)

The Broken Links check in the Site Health scan sends HTTP HEAD requests (and, where a server refuses HEAD, a single ranged GET) to the links found in your 50 most recent published posts and pages, to see whether they still resolve. The request identifies this plugin and your site URL in its user agent. No personal user data is transmitted. Results are cached for 12 hours. This runs when you start a scan from the admin, and during the scheduled scan if you leave that enabled — on sites with more than 500 published posts the link check is skipped on the schedule. Turning scheduled reports off in My Site Hand Settings stops the scheduled scan entirely.

Requests this plugin makes to your own site

The Exposed WordPress Files and XML-RPC checks ask your own site, over HTTP, whether /readme.html, /license.txt, /wp-config-sample.php, /wp-content/debug.log and /xmlrpc.php answer to an anonymous visitor. These are loopback requests to your own domain, not to any third party, and no data is sent in them. Results are cached for 12 hours. If your host blocks loopback requests, both checks report that they could not run rather than reporting your files as safe.

Shared report links

Creating a share link stores a redacted snapshot of your scan in your own database and serves it from your own site at a tokenized URL. Nothing is uploaded anywhere. The page is sent with X-Robots-Tag: noindex, nofollow, every link expires, and you can revoke one at any time.

No data is sent to any third-party analytics or tracking service by this plugin.

Скриншоттор

Орнотуу

Install & Activate: Search for My Site Hand in your WordPress dashboard, install, and activate it. You land on Site Health and the first scan starts by itself. That is the whole setup.

Connecting an AI assistant is optional, and fully guided:

  1. Install & Activate: Search for My Site Hand in your WordPress dashboard, install, and activate it.
  2. Generate a Token: Go to My Site Hand > API Tokens and click Create Token. Give it a label (e.g. “Claude Desktop”).
  3. Connect in Seconds: Go to the How to Use page in your dashboard:
    • Step 1: Copy and run the command to install the mcp-remote bridge on your computer.
    • Step 2: Copy the auto-generated connection command (it includes your secure token) and run it in your terminal.
  4. Restart & Use: Restart your Claude Desktop app, and start talking to your website!

FAQ.KG

Do I need an AI assistant, an API key or a token to use this?

No. The Site Health scan and Quick Fix work on their own, with nothing to install and nothing to configure. Connecting Claude, Cursor or VS Code is an optional upgrade, not a requirement.

What does the scan actually check?

Twelve things. Broken links in your 50 most recent posts and pages; images with no alternative text; published posts and pages with no SEO meta description (Yoast SEO or RankMath); oversized media; files that nothing on your site appears to use; platform problems such as pending updates, an outdated PHP version, missing HTTPS or a stalled cron; images with no width or height; images opted out of lazy loading; WordPress files left publicly readable; whether xmlrpc.php answers; pages with very little content; and four structural accessibility problems.

What does a shared report link show the person I send it to?

The score, the name of each check, and how many issues each one found. Nothing else. No file names, no page addresses, no server paths, no post or media IDs, no edit links, and no plugin, theme, PHP or WordPress version numbers. The two security checks are excluded from public reports entirely. Every link expires — 7, 30 or 90 days, your choice — and you can revoke one at any time.

Does the “Download PDF” button make a PDF on my server?

No, and deliberately so. It opens a clean printable page and your browser’s own print dialog, where you choose “Save as PDF”. Bundling a PDF library would multiply the size of the plugin to do something every browser already does well.

Should I turn XML-RPC off because the scan mentions it?

Only if you do not use the WordPress mobile app, Jetpack, or a desktop publishing tool — all of which need it. That is why it is reported as a notice rather than a warning, and why sites running Jetpack are skipped entirely. Disabling it on a site that needs it breaks that site, which is worse than leaving it alone.

Will it report links that are not really broken?

It tries hard not to. Only 404 and 410 count as gone. Anything ambiguous — a 403, a 405, a server error — is retried a different way, and if it is still unclear the link is not reported at all. A single false alarm would make you distrust the whole report.

Does the scan slow my site down?

No. It runs only when you start it, or on the schedule you choose, and it works in small batches so no single request runs long enough to time out. Scheduled scans skip the link check on sites with more than 500 published posts.

Do I need Node.js?

Not for the Site Health scan or Quick Fix. Node.js is only needed if you choose to connect an AI assistant, because the desktop bridge (mcp-remote) runs on your own computer.

Is this plugin secure?

Yes. Security is our top priority. The plugin uses secure, SHA-256 hashed API tokens. You choose exactly which permissions to grant to each token, and you can revoke access instantly at any time. Furthermore, the built-in Audit Log shows you exactly what commands were run, who ran them, and when.

What AI applications are supported?

Any application that supports the Model Context Protocol (MCP). This includes Claude Desktop, Cursor IDE, VS Code (via MCP extensions), and Windsurf.

Do I need to edit JSON configuration files?

No! Unlike other MCP setups that force you to search for hidden directories and edit configuration files manually, My Site Hand uses a lightweight Node bridge utility to write the configuration for you automatically.

Does this send my data to third-party servers?

No. All MCP communications occur directly between your local AI client and your WordPress site. The plugin does not track, collect, or store your private data on external servers.

Сын-пикирлер

Август 22, 2026-ж. 3 replies
The author helped me with a setup issue. Great!
Июнь 1, 2026-ж. 1 reply
My Site Hand (AI) has completely changed how I manage my WordPress site. Instead of digging through menus and settings, I can simply tell the AI what I want, and it handles the work for me. The plugin is fast, intuitive, and surprisingly powerful. Creating content, managing pages, handling SEO tasks, and performing routine site management feels effortless. The interface is clean, and the AI understands instructions very well.What impressed me most is how much time it saves. Tasks that normally take several minutes can now be completed with a simple conversation.If you’re looking for a smarter way to manage your WordPress website, I highly recommend giving My Site Hand (AI) a try. Excited to see how it evolves in future updates!
Read all 2 reviews

Contributors & Developers

“My Site Hand – AI Assistant, Site Health & MCP Server for WordPress” is open source software. The following people have contributed to this plugin.

Мүчөлөрү

Өзгөртүүлөр

1.2.0 – 6 September 2026

  • New: six more checks — image dimensions, lazy loading, exposed WordPress files, XML-RPC, thin content, and accessibility basics. Twelve checks in total.
  • New: PDF and CSV export. Send a client the report without giving them a login.
  • New: shareable report links with an expiry you choose. Public reports show scores and counts only — never paths, IDs, versions or plugin names.
  • New: Bengali translation, and the plugin is now fully ready for community translation.
  • Improved: Score weighting was retuned for twelve checks, so an ordinary site still lands in a usable range rather than being marked critical for having twice as much measured.

1.1.0 – 26 August 2026

  • New: Site Health Scan — one click, no setup. Find broken links, missing alt text, missing meta descriptions, oversized media, orphaned files, and plugin or core health problems.
  • New: Quick Fix — repair issues inline from the report. No AI or API key required.
  • New: Score history and trend so you can watch your site improve.
  • New: Optional weekly email report. It stays quiet when there is nothing new to say.
  • New: Plugin checks now appear in WordPress’s own Tools Site Health.
  • Improved: Activation now takes you straight to a scan of your site instead of setup instructions. The MCP connection steps are still there, collapsed on the Dashboard as an optional upgrade.
  • New: Redesigned admin interface. The left sidebar is replaced by a brand row and a tab bar, and every page now has a numbered index so you can jump straight to the section you came for.
  • Improved: A single accent colour, flat surfaces, and a monospaced type scale make status, counts, and destructive actions easier to read at a glance.
  • Improved: The dashboard now surfaces what needs your attention — missing HTTPS, tokens expiring within 30 days, or a stopped endpoint.
  • Fixed: The “Trust proxy headers” and “Allow token in URL query string” settings did not save. Both now work.
  • Fixed: The settings page could submit itself and blank stored options if you pressed Enter in a text field. Settings save individually as you change them, so the form has been removed.

1.0.2 – 24 August 2026

  • Security: Tokens created without an explicit ability selection no longer default to full access. Existing tokens are migrated automatically and continue to work unchanged.
  • Security: API tokens are no longer accepted via URL query string by default. Use the Authorization header instead. An opt-in setting remains available for clients that cannot send headers.
  • New: Optional per-token IP allowlist with CIDR range support.
  • New: Trusted proxy setting for sites behind Cloudflare or a reverse proxy.
  • Improved: Token creation now clearly distinguishes full access from limited access.
  • Fixed: Database schema version was not being stored after an upgrade, causing unnecessary schema checks on every page load.

= 1.0.1 – 9 June 2026=
* Added a “Suggest a Feature” page so users can submit feature requests directly to the developer’s email.
* Improved email deliverability with dynamic “From” headers and real-time failure log captures.
* Styled and aligned the admin menu icon in the sidebar with a white background and centered flex alignment.
* Added automatic redirection to the dashboard immediately upon plugin activation for faster onboarding.
* Added a “How to Use” shortcut link directly on the Plugins page.

1.0.0

  • Official Initial Release.
  • Automated zero-config setup for Claude Desktop.
  • Support for Content, SEO (Yoast, RankMath), WooCommerce, and Diagnostics.
  • Secure token management and real-time audit logs.