Integration

redirection.io integration

redirection.io manages the HTTP redirections and traffic rules of websites. Create simple redirects or full rules (triggers, markers and actions such as redirections, custom headers or status codes), review the pending draft changes and publish them, find rules by their exact source URL, read a rule's hit statistics, and manage the projects, domains and agent instances of the organization. The public API needs an organization with at least one project on a Starter or Pro plan and is rate limited to 10 requests per minute (publication: 20 per day). Authentication is an organization API token, created under Settings > API tokens in the manager and sent as a Bearer token.

Connect redirection.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in redirection.io.Built from the 24 redirection.io tools below, on the connection you add once.

What you can do with redirection.io

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Rule, 5 operations

create_ruleCreate rulePOSTCreates a full traffic rule (trigger, markers, variables, actions such as redirection, header, customStatus or customHtml, and test examples) as a draft change. It applies after publish_project.
delete_ruleDelete ruleDELETEMarks a rule for deletion by creating a delete draft change; the rule is removed when the project is next published and can still be recovered from the project history.
get_ruleGet ruleGETReturns one published rule: trigger, actions, markers, variables, examples, tags, priority, enabled state, usage count and last use.
list_rulesList rulesGETLists the published rules of a project (100 per page, sorted by id) with trigger, actions, markers, tags and usage. Drafts are not included. Filter by tags, enabled or exact source URL.
update_ruleUpdate rulePUTUpdates an existing rule (trigger, actions, markers, variables, examples, tags, priority, enabled) as an update draft change; the website uses the new version once the project is published.

Domain, 4 operations

create_domainCreate domainPOSTAdds a domain to a project for redirection.io managed instances. The answer lists the DNS records (a TXT and an A or CNAME) to create at your DNS provider and whether DNS is already valid.
delete_domainDelete domainDELETEPermanently removes a domain from its project. Remove its DNS records afterwards.
get_domainGet domainGETReturns one domain of a project: DNS validity, the DNS records to create with their detected and required values, SSL settings and backend options.
list_domainsList domainsGETLists the domains of a project served by redirection.io managed instances (100 per page), with DNS validity, the DNS records to create, SSL settings and the backend each forwards to.

Project, 4 operations

create_projectCreate projectPOSTCreates a project in the organization. metadata can carry your own key/value information about it.
delete_projectDelete projectDELETEPermanently deletes a project with all its rules, logs and data. This cannot be undone.
get_projectGet projectGETReturns one project: id, name, slug, plan and metadata.
list_projectsList projectsGETLists the projects of the organization the API token belongs to, with id, name, slug, plan and metadata.

Draft, 3 operations

delete_draftDelete draftDELETEDiscards one draft change before publication: an add is dropped, an update or delete is cancelled and the published rule stays as it is. A discarded draft cannot be recovered.
get_draftGet draftGETReturns one draft change: its status (add, update or delete) and the full rule it would publish.
list_draftsList draftsGETLists the unpublished draft changes of a project (100 per page): each has a status (add, update or delete) and the full rule. Filter by tags, enabled or exact source URL; publish_project applies them.

Instance, 3 operations

delete_instanceDelete instanceDELETEPermanently deletes an agent instance from a project.
get_instanceGet instanceGETReturns one agent instance of a project: name, agent version and its status, rule count, last rules update, logging state, last log flush and whether it is misconfigured.
list_instancesList instancesGETLists the redirection.io agent instances connected to a project, with agent version and its status, rule count, last rules update, logging state and last log flush.

Ip, 1 operation

list_ipsList ipsGETLists the IPv4 addresses that redirection.io managed instances use to forward requests to your backend, for example to allow them in a firewall.

Organization, 1 operation

get_organizationGet organizationGETReturns the organization the API token belongs to (id, name, slug) and its projects with id, name, slug and plan. Start here to find the project id the other tools need.

Publish, 1 operation

publish_projectPublish projectPOSTPublishes every draft change of a project (adds, updates and deletes) so the redirection.io agents apply them. Limited to 20 calls per day.

Redirection, 1 operation

create_redirectionCreate redirectionPOSTCreates a simple redirect (source URL, target URL, status code 301, 302, 307 or 308) as a draft change with status add. The website uses it only after publish_project.

Statistic, 1 operation

get_rule_statisticsGet rule statisticsGETReturns the hit counts of a rule over time, grouped by an interval of at least one hour (around 100 data points), between start and end, or since the rule's creation when no range is given.

Use redirection.io from Claude Code, Cursor or Codex

Connect redirection.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its redirection.io operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect redirection.io

Create your workspace
Sign up free. Nothing to install.
Connect redirection.io once
Add your redirection.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.