Use AISA from Claude (and from ChatGPT)
From version 2.0, AISA makes its SEO tools available to AI assistants. Open Claude, type "audit the SEO of the Contact page and apply the fixes", and AISA does the work on your site. You stay in control: every action goes through the permissions of your WordPress user, and anything written leaves a revision or a backup behind.
What MCP is, without the jargon
MCP is the standard way an AI assistant connects to an external service. Think of a power socket: the assistant on one side, your site on the other. Claude, ChatGPT and the others know how to use that socket; AISA provides it.
Underneath is the WordPress Abilities API, introduced in version 6.9: a registry where each plugin declares what it can do. AISA registers 13 abilities there. Any MCP connector that reads the registry can see them.
What you need
- WordPress 6.9 or later (the Abilities API ships with core from that version).
- AISA 2.0 active, with the Brand Context filled in and an AI provider configured, or AISA Cloud.
- A WordPress application password for your user.
- AISA Premium, the separate companion plugin, if you also want the tools that write. It must be on the same version as AISA (2.0 or later): the tools that write live inside it.
Abilities are on by default in 2.0. The switch and the real status of your site are in AISA → Settings → API Keys, section Abilities API & MCP.
The WordPress application password
It is a secondary password tied to your user. Create it in wp-admin → Users → Profile → Application Passwords, give it a name such as "Claude", and copy it straight away: WordPress shows it only once. You can revoke it from the same page at any time. Claude uses it to identify itself to the site as you, with exactly your permissions; your login password is never involved.
Three ways to connect
1. AISA on its own
AISA has a built-in MCP endpoint: https://yoursite.com/wp-json/aisa/v1/mcp. No extra plugin.
In Claude Code, one line is enough:
claude mcp add --transport http aisa https://yoursite.com/wp-json/aisa/v1/mcp \
--header "Authorization: Basic BASE64"
where BASE64 is user:password encoded (on a Mac: printf 'user:xxxx xxxx xxxx' | base64). For Claude Desktop the configuration lives in claude_desktop_config.json, using the mcp-remote bridge and the same header.
This is the right choice when your job is SEO. It exposes AISA only, so for "optimize the Contact page" Claude first has to find the page id, which it does with the standard WordPress API — not always on the first try.
2. A connector that handles the whole of WordPress
If you want the assistant to do the rest as well — create drafts, upload images, tidy menus — you need a general connector. Two of them read the abilities registry and therefore show AISA too:
- MCP Adapter, the official WordPress plugin. One address with the abilities of core, of AISA and of any other plugin. With the Adapter installed, AISA also exposes
https://yoursite.com/wp-json/aisa/mcpcarrying only theaisa_*tools. - Easy MCP AI, free. It discovers abilities, adds WordPress tools of its own and the OAuth flow that ChatGPT and the claude.ai web app require. AISA abilities have to be ticked in its Abilities page, and consent granted after ticking them.
Other connectors today expose only their own tools, so AISA does not appear there. Do not keep two OAuth connectors on the same site: they compete for the same addresses and one of them stops authorizing.
3. Staging and local sites
With Claude running on your own computer none of this is needed: it connects to the local site, http://yoursite.local/wp-json/aisa/v1/mcp, with the same application password. Use http, not https. Claude Code also has the terminal and WP-CLI, so on a local site it can handle the rest without connectors. Only the claude.ai web app and ChatGPT cannot reach a local site: those need the public one.
The 13 tools
Five of them read and are in the free plugin; eight write and need AISA Premium, the separate companion plugin.
The names below are the ones your assistant sees; the technical ability name is in brackets, useful only if you go and look at the tool list in your client.
| Tool | Type | What it does |
|---|---|---|
Get SEO status (aisa/get-seo-status) |
read | title, meta description, focus keyphrase and slug of a content item, active SEO plugin, detected language, when AISA generated it and where it wrote |
Audit a page (aisa/audit-page) |
read | the on-page checks with the outcome of each one; on request, also the public page served to visitors |
Get llms.txt (aisa/get-llms) |
read | the document that describes the site to AI answer engines, its URL, who owns the file and how many contents already carry an AI Search Context |
Get the Brand Context (aisa/get-brand) |
read | who you are, who you serve, tone of voice, selling points, terms never to translate |
Diagnostics (aisa/diagnostics) |
read | how AISA is set up: versions, SEO plugin and mode, providers by name, Cloud and credits. Never keys |
Optimize a page (aisa/optimize-page) |
write | generates focus keyphrase, SEO title, meta description, AI Search Context and, on request, the slug |
Auto-fix a page (aisa/autofix-page) |
write | repairs the failing audit checks; slug, H1 and content only if you ask for them |
Optimize many pages (aisa/optimize-bulk) |
write | a batch of contents as a job, with an id returned immediately |
Get a background job (aisa/get-job) |
read | progress and per-item outcome; what is still queued can be stopped |
Set the Brand Context (aisa/set-brand) |
write | updates the fields you name, leaves the others untouched |
Describe images (aisa/media-alt) |
write | alt text and title with AI Vision: only what is empty, the alt only, or everything from scratch |
Check and repair internal links (aisa/links-fix) |
read or write | report of broken internal links (read only) and, if you ask, repair with 301 redirects |
Scan AI visibility (aisa/geo-scan) |
write | whether AI answers cite your site and who is cited instead: cost estimate first, scan afterwards |
Nine sentences to try
- "Run the AISA diagnostics on this site."
- "Give me the SEO status of page 42: title, meta description, focus keyphrase and slug."
- "Audit page 42, apply the fixes, then audit it again and tell me what changed."
- "Optimize in the background the twenty published pages with no meta description and tell me when it is done."
- "Write the alt text for the images of post 18 that still have none."
- "Check the internal links of page 42 and repair the safe ones with redirects."
- "Add these to the do-not-translate terms: AISA, One-Click SEO, AISA Cloud."
- "How much would an AI visibility scan on 'WordPress SEO plugin' cost? Estimate only."
- "Did page 42 really reach the front end? Verify on the live page."
Actions that change what visitors see — slug, H1, content — are off by default and have to be asked for explicitly.
What to expect
| Situation | Answer |
|---|---|
| A write action without AISA Premium | a clear refusal: the tools that write are not in the free plugin |
| A page your user cannot edit | refused: the permissions of the application password user apply |
| A content fix with no focus keyphrase | you are asked to set or generate one first |
| An AI visibility scan | the cost estimate first, the scan only after you confirm |
| "Where is my OpenAI key?" | never returned: diagnostics only says whether a provider is configured |
| A background job still running | you can ask for progress or stop it; what is written stays written |
| Doubt about the result | ask for the check on the live page: AISA reads the page as served and compares title, description and social image with what was saved |
| Too many calls in a row | per-user limits, per minute: 60 reads, 10 writes, 2 job starts, 2 AI visibility scans |
Security
- Every call goes through WordPress authentication and capabilities, exactly as if you were in wp-admin.
- API keys, licences and tokens cannot be reached by any tool: diagnostics only reports whether a provider is configured.
- SEO writes go through the adapter of the active SEO plugin, so no duplicate fields are created.
- The Brand Context can only be written in the listed fields: an assistant cannot invent a field and have it saved.
- Abilities can be switched off with one click in Settings → API Keys, or from
wp-config.phpwithdefine( 'AISA_ABILITIES', false );. - The free plugin exposes read-only tools only.
Frequently asked questions
I updated AISA to 2.0 but the assistant only sees the tools that read. Why? Because AISA Premium is still on an earlier version. The two plugins update through different channels: AISA comes from WordPress.org, AISA Premium from ours. With mismatched versions the site keeps working — One-Click, Batch and the rest carry on — but the eight tools that write appear only once AISA Premium is on 2.0 as well. Go to Plugins, update AISA Premium and, so you never have to think about it again, turn on "Enable auto-updates" next to it: from then on the two plugins stay aligned by themselves.
Do I have to install another plugin? No. For SEO, AISA is enough. A general connector is only needed if you also want to manage the rest of the site from the chat.
Does it work with ChatGPT? Yes, through a connector that adds the OAuth flow ChatGPT requires, such as Easy MCP AI. The built-in AISA endpoint is designed for Claude Code and Claude Desktop.
What about Yoast or Rank Math? They are supported. AISA works as a copilot of the active SEO plugin and writes into its fields, with no duplication. The same goes for SEOPress and AIOSEO.
What does it cost? The read tools are in the free plugin. The tools that write require AISA Premium and spend your own AI providers or your AISA Cloud credits, exactly as they do from the interface. An AI visibility scan always asks for confirmation before spending.
Can I undo? Yes. Before touching a content item AISA saves a WordPress revision and, with Elementor, a backup of the builder data. Stopping a job does not undo what has already been written: that is restored from the revisions.
How do I know the connection works? Type "Run the AISA diagnostics on this site": if it answers with the version, the detected SEO plugin and the configured providers, you are connected.