A brief becomes a real page.Redirection MCP integration
Fix the 404s and keep every old link working.
EMCP works through the Redirection plugin's own classes, so a redirect your AI creates shows up in Redirection and runs like one you made there. Read the redirect and 404 logs without visitor details, create exact URL redirects, and change or retire them with a version check. Edits can be undone from History.
Free integrationRedirection 5.10.1
One log, a few redirects
| Step | What EMCP does |
|---|---|
| 01 · 404 log | Missing URLs, visitor details removed |
| 02 · Propose | Source, target and code for each |
| 03 · Create | 301 redirects, loops refused |
| 04 · History | Each new redirect undoable |
A practical place to start
From a 404 report to working redirects.
- 01
Read the 404s
list-404s returns the missing URLs Redirection logged, without IP addresses, user agents or referrers. list-redirects shows what already exists.
- 02
Create the redirects
create-redirect takes a site-relative source, a local path or HTTP(S) target, a WordPress-module group and a code. A redirect that would loop on this site is refused.
- 03
Retire or adjust later
update-redirect, disable-redirect and delete-redirect name the version they read, so a change made in the meantime is never overwritten.
Built for Redirection
The Redirection plugin you already use
EMCP calls Redirection’s own redirect and group classes, so everything your AI does appears in Redirection’s screens with the same groups, codes and hit counters. Redirection is separate from EMCP’s own Redirect Manager: use this integration when Redirection is the plugin handling your redirects.
Logs without visitor details
list-logs and list-404s return the requested URLs, dates and status, and leave out IP addresses, user agents, referrers, headers and request data. That is enough to plan redirects without sending visitor details to the AI.
Safe changes
Sources must be paths on this site; targets are a local path or an HTTP(S) URL without credentials. A redirect that would send visitors round in a loop through other redirects on the site is refused. Every write needs confirm: true, dry_run: true checks it first, and an edit that fails halfway is put back. Every change is in History in EMCP Tools or EMCP Lite.
Use the Redirection tool reference for operation names and arguments, and LiteSpeed Cache to purge a page after its redirect changes.
Get connected
Put Redirection in your AI’s toolkit.
- 1
Install Redirection
Install EMCP Tools 3.21.1 or later, or EMCP Lite 1.0.5 from WordPress.org, with Redirection 5.10.1 and its database setup finished. Other Redirection versions are refused until they are qualified.
- 2
Enable the write tool
redirection-read is on; redirection-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > Redirection and reconnect your AI client.
- 3
Ask for a cleanup
Ask your AI to read the 404 log and propose redirects before creating any.
Then connect Claude Code, Claude Desktop, or Cursor to use the Redirection tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Redirection, supported operations, and the workflow on your site.
Does it follow the target URL to check it?
No request is made to any target. EMCP checks the format and looks for a loop through redirects already stored on this site.
Which groups can it use?
Groups handled by WordPress. Groups for Apache or Nginx are read but never written, because Redirection writes those to server files.
What does a version protect?
Each redirect's version covers the redirect and its group; a group's version covers all its redirects. A change made since your read is refused with a conflict.
Can I undo a deleted redirect?
No. Deleting is recorded in History but cannot be undone, so the AI should disable a redirect first when you might want it back.
Your tools. Your WordPress site.