RedirHub MCP Server

Control every link from your AI assistant. Create branded links, dynamic QR codes, domain redirects and whole website migrations, then manage, audit and measure them through a standardized protocol, compatible with Claude, ChatGPT, Cursor and any MCP client.

RedirHub is redirect infrastructure. This MCP server gives your AI agents direct access to that infrastructure: create and manage links, connect domains, invite team members and query analytics, all without opening a dashboard.

Features

• One model for every link: branded links, dynamic QR codes, domain redirects and website migrations are created by intent and managed as one kind of object, as in the dashboard.

• QR codes your agent can hand over: create-qr-code and get-qr-code return the QR code image itself, drawn exactly as the dashboard draws it.

• Safe bulk changes: bulk tools preview by default and only apply changes with a confirmation token from that preview.

• Same rules as the dashboard: links created or updated here go through the same validation, plan features and limits as the dashboard and the REST API.

• Analytics & logs: query click statistics, raw access logs and each link's change history.

• Team collaboration: multi-member workspaces with role-based access control.

• Sign in, no token to copy: assistants connect with OAuth. You sign in to RedirHub, pick the workspace and choose what the assistant may do; disconnect it any time.

• MCP protocol: works with Claude, ChatGPT, Cursor, Cline and any MCP client that calls tools.

Related MCP server: Daemoon

Endpoint

https://mcp.redirhub.com/mcp/v1

Authentication

Sign in with OAuth (recommended)

Add the endpoint to your assistant and it sends you to RedirHub to sign in. There is no token to copy:

1. Sign in to RedirHub (or switch account).

2. Pick the workspace the assistant works in. Each connection works in one workspace.

3. Choose what it may do (below) and select Allow access.

The assistant is then listed in Account → AI assistants (account.redirhub.com/mcp), where you, or a workspace manager, can disconnect it. Disconnecting revokes its access at once; the links it made stay.

The assistant only sees the tools it was granted. Calling another one returns an error naming the permission it needs; to grant more, disconnect the assistant and connect it again.

For client developers: the server follows the MCP authorization spec. A request without a token gets 401 with a WWW-Authenticate header pointing at the protected resource metadata (https://mcp.redirhub.com/.well-known/oauth-protected-resource/mcp/v1). The authorization server is https://account.redirhub.com (metadata at /.well-known/oauth-authorization-server). It supports:

• dynamic client registration (/oauth/register);

• the authorization code flow with PKCE (S256);

• refresh tokens.

Access tokens last an hour and refresh tokens 30 days.

API token

For scripts and clients that can't sign in, generate a Workspace API token from dash.redirhub.com (Settings → API Tokens) and pass it as a Bearer token:

Authorization: Bearer ***

An API token has every tool. It acts in the workspace it was created for, within your role: changing links and domains needs the editor role; workspace settings and members need the manager role.

Both ways are available on all plans, including Free.

Server Info

• Name: Redirect Infra Public API

• Version: 1.2.0

• Transport: Streamable HTTP (JSON-RPC 2.0)

Data Model

Users belong to workspaces (organizations). A workspace has custom domains (hosts) and links.

Links are created from four intents but managed as one kind of object:

Every link has an id (e.g. link_7bXmR4) that the get-link, update-link, delete-link, get-qr-code and get-link-history tools take. Domains are addressed by hostname, members by id (e.g. user_zwbJjgb8).

Tools

Links: read

Links: create

Use list-hosts with short_links_enabled: true to find the domains branded links and QR codes can use.

Links: manage

⚠️ Bulk operation safety

bulk-update-links, bulk-delete-links and bulk-import only preview unless called with dry_run: false:

1. Call without dry_run. The preview returns the affected count, a sample of the affected URLs and, for changes and deletions, a confirmation_token.

2. Show the count to the user.

3. Only after the user confirms, call again with the same arguments, dry_run: false and the confirmation_token.

The server enforces this: bulk-update-links, bulk-delete-links and bulk-import in upsert mode refuse to apply changes without a token issued for exactly the same arguments, by the same user, in the same workspace, within the last one to two hours.

Domains

Workspace & members

Account

📊 Statistics

QR codes

create-qr-code and get-qr-code return the code as a 512 px PNG, drawn exactly as the dashboard draws it: same modules, colors, margin, workspace logo and readable link underneath. The code encodes the link with ?utm_source=qr, so scans are counted separately from clicks.

For print files, the REST API serves the same code as SVG or PNG (512, 1024 or 2048 px wide):

GET https://api.redirhub.com/v1/links/{id}/qr              # SVG
GET https://api.redirhub.com/v1/links/{id}/qr?format=png&width=2048

Resources

Clients that attach MCP resources can also read the same data as resources (append query params as ?key=value): redirects://list, redirects://link_{id}, redirects://count, links://list, links://link_{id}, hosts://list, hosts://{hostname}, workspace://current, members://list, members://{user_id}, account://me, plugins://catalog and record-types://catalog.

Most clients only let the model call tools, so prefer the tools above; they cover everything the resources do.

Renamed tools

Version 1.1 dropped the -tool suffix and named the record tools after links. The old names keep working, so existing setups don't break, but new prompts and integrations should use the new ones:

Other changes in 1.1:

• Create tools return the link. create-redirect used to wrap it in {created, record}.

• Bulk tools preview by default. They used to apply changes unless told otherwise.

• bulk-update-links needs a filter or all_links: true. It used to change every record in the workspace.

Quick Start

1. Add the server to your assistant

Claude (claude.ai, Claude Desktop): Settings → Connectors → Add custom connector, name it RedirHub and paste https://mcp.redirhub.com/mcp/v1.

ChatGPT: Settings → Apps & Connectors, add a custom connector with the same URL.

Cursor: Settings → MCP → Add new MCP server, or in mcp.json:

{
  "mcpServers": {
    "redirhub": {
      "url": "https://mcp.redirhub.com/mcp/v1"
    }
  }
}

Any other MCP client: add a remote (Streamable HTTP) server with the same URL. To try it from a terminal:

npx @modelcontextprotocol/inspector --transport http --server-url https://mcp.redirhub.com/mcp/v1

2. Sign in and choose what it can do

Your assistant opens RedirHub: sign in, pick a workspace and the permissions, and select Allow access. You're sent back to the assistant, connected.

Create a Workspace API token from dash.redirhub.com Settings → API Tokens and send it as a header:

{
  "mcpServers": {
    "redirhub": {
      "url": "https://mcp.redirhub.com/mcp/v1",
      "headers": {
        "Authorization": "Bearer rh_YOUR_API_TOKEN"
      }
    }
  }
}

3. Use it

Once connected, tell your AI agent what you need:

"Create a QR code for our menu on go.acme.co that points to acme.com/menu, and show it to me."

"Redirect old.acme.co to acme.com with a 301, keeping the path."

"Migrate these 500 URLs from our old site to the new one."

"How many links on go.acme.co had no clicks in the last four weeks? Pause every link on that domain."

"Who changed the destination of go.acme.co/spring, and when?"

Documentation

• API Reference: full RedirHub API docs

• dash.redirhub.com: web dashboard

• MCP Specification: protocol docs

Built by RedirHub: redirect infrastructure for teams that can't afford broken links.