A Monday morning, in one conversation
Nothing is simulated below: every chip is one of the thirteen tools the server exposes.
You
I renamed a few pages last week. What did that break?
Assistant
list_logs
Three pages account for almost all of them:
The first two look like pages you renamed. Want me to redirect them?
You
Yes, to the pages that replaced them. Check nothing else conflicts.
Assistant
check_rule_impact create_http_rule
I replayed both against your whole rule set before writing them. The first one is clean. The second was caught by your catch-all on /shop*, so I gave it a higher priority.
Both are drafts. Nothing has changed for your visitors yet.
You
Looks good, publish.
Assistant
publish_rules
Published. Both redirections are live, and the publication is in your project history under your name.
What it can do
Read your traffic
Every request your agents handled, counted and grouped on demand, over the whole retention of your plan.
Write and change rules
Any trigger and any action redirection.io supports, from a plain 301 to a backend switch. Markers and variables included.
Check before writing
Your examples are replayed against the whole rule set, and the answer names the rule that gets in the way.
Look after your domains
Which domains are configured, whether their DNS is valid, and the exact records still missing.
Connect your client
No API key to copy, no secret to paste in a configuration file: you sign in once, in your browser.
1
Point your client at the server
The whole configuration is one URL:
https://redirection.io/mcp
2
Choose what it may do
Your client sends you to redirection.io, where you sign in and approve the permissions it asked for, one by one.
3
Ask
Your assistant now sees your projects. Talk to it about your redirections the way you would to a colleague who has the manager open.
Claude Code, GitHub Copilot CLI
$ claude mcp add --transport http redirectionio https://redirection.io/mcpClaude Desktop, claude.ai, ChatGPT
Open the connector settings of your client and add a custom connector with that URL. Editing claude_desktop_config.json by hand does not work, that file is for servers running on your machine.
Cursor, and clients configured in JSON
{
"mcpServers": {
"redirectionio": {
"url": "https://redirection.io/mcp"
}
}
}Things worth asking it
“Which URLs of my site returned a 404 this week, and how often?”
“Redirect every page of /old-blog to its equivalent under /blog, and show me what it would do before writing anything.”
“Which of my rules have never matched a single request?”
“Add a Content-Security-Policy header on the whole site, except on /embed.”
“Is the DNS of shop.example.com correctly configured? What is missing?”
“Summarise what changed in my rules since last Monday.”
You decide what it may do
These are the permissions your client asks for, and the wording you will read on the authorization screen.
| Permission | What it allows |
|---|---|
mcp |
List the projects you have access to |
mcp:logs:read |
Read the logs of your projects |
mcp:rules:read |
Read the rules of your projects |
mcp:rules:write |
Create, change and delete rules in your projects |
mcp:rules:publish |
Publish the pending rule changes of your projects |
mcp:domains:read |
Read the domains of your projects |
mcp:domains:write |
Add and delete domains in your projects |
Safe by construction
Nothing goes live on its own
A rule an assistant creates, changes or deletes is a draft, exactly like a rule you write yourself. It waits in your pending changes until the project is published.
Publishing is a permission apart
Refuse it and the assistant cannot reach your visitors at all, whatever else it is allowed to do. You review and publish from the manager, with the last word.
Your own rights still apply
The connection acts as you: it sees the projects you see, and it cannot do anything in them that you could not do yourself.
Start talking to your redirections
The server is included in every plan. Connecting a client takes a minute, and you can revoke it at any time from your account.