Redirection + MCP: let AI manage redirects and clear your 404 log

Every site that has lived a while has a Redirection list that nobody fully understands, and a 404 log nobody reads. After a migration or a URL cleanup, both get worse. NibWP exposes Redirection as typed MCP tools — list and read redirects and 404s, create and update redirects — so an agent can do the tedious part: build the map, check it, and keep it clean.

Hand it a list of old → new URLs and get 301s, with chains flagged before they are created. Ask what is 404ing most this month and get redirects proposed for the ones with an obvious target. Find redirects whose target is itself redirected, or returns 404, and fix them. Plan first, log after.

Redirection is one of the 45+ integrations inside NibWP's WordPress MCP server — 4 typed Redirection tools on top of 190+ WordPress tools. The full tool reference lives on the Redirection integration page; this page is about what those tools let you do.

What AI can do in Redirection

The Redirection tools NibWP exposes

Every Redirection capability is a typed MCP tool with a schema the AI client can read, so it calls the right thing with the right arguments instead of guessing at your database. Read tools are free to explore; write tools go through the approval flow.

• nibwp/redirection-manage — Manage Redirection: create, edit, enable, disable and delete redirects, organize them into groups, read the redirect log and the 404…

Example prompts

Plain English is the interface. These are the kinds of requests agencies run against Redirection every day:

• “Create 301s for these 80 old → new URLs and tell me which ones would chain.”
• “What are the top 50 404s this month? Propose redirects for the ones with an obvious target.”
• “Find redirects whose target returns 404 or is itself redirected.”
• “Add a regex rule sending /blog/(.*) to /guides/$1 as 301.”
• “Disable every redirect in the 'Old campaign' group.”

How it works with Redirection

There is no new dashboard to learn. You describe an outcome, NibWP plans it, and you approve before anything is written.

1. Connect — install NibWP, connect Claude, Cursor, ChatGPT or any MCP client. Redirection is detected automatically and its tools appear in the client.
2. Describe — hand it the map, the rule or the question. NibWP reads the current redirects and the 404 log first and shows the plan — including chains — before creating anything.
3. Approve — NibWP shows the plan: which records it will create or change, and what will stay untouched. Nothing happens until you say yes.
4. Done — it writes real Redirection data through the plugin's own APIs and reports back in plain English, with every change in the audit log.

Why not just a generic AI?

A general-purpose assistant can write text about Redirection; it cannot safely operate it. The difference is structure, context and control.

A generic assistant

• Gives you a CSV to import and hopes for the best
• Cannot see your existing redirects or your 404 log
• Creates chains and loops because it cannot check targets

Redirection + NibWP

• Creates and updates redirects through the plugin, chains flagged first
• Reads the 404 log and proposes fixes
• Audits targets and collapses chains to one hop

Safe by default

NibWP is built for agencies running client sites, so control and traceability come first:

• Nothing is written without your approval — you see the plan first, and you can run in draft mode.
• Every action is recorded in a full audit trail, per site and per user.
• It runs on Redirection's own functions and APIs — your data stays on your server, nothing is copied to a third-party service.
• Deleting redirects is never part of an ordinary connection — disable is the reversible default.

Related integrations

Most sites pair Redirection with other plugins NibWP already speaks: SEOPress + MCP, Yoast + MCP, Rank Math + MCP, Slim SEO + MCP, WordPress + MCP, Weglot + MCP. All of them ship in the same plugin — see pricing for what each plan includes.