MCP

Connect Claude Code, VS Code, Codex, Cursor, Claude Desktop, and other MCP clients to redirect.pizza, and manage your redirects in chat. It is the same team, the same API token, and the same scopes as the REST API.

Open the API/MCP page

What you can do

Once connected, you can ask your client to:

  • Create, update, pause, and import redirects
  • Manage domains and DNS, including Automatic DNS
  • Set up email forwards
  • Check analytics
  • Invite teammates
  • Test a URL or generate a QR code

Hostnames are created for you from your redirect sources. Point DNS at redirect.pizza and the redirect goes live with automatic HTTPS.

Getting started

Open the API/MCP page in your account, create an API token, and copy the sample config for your client. Replace the highlighted placeholder with your token.

Need a hand with Claude Desktop? Use the mcp-remote sample on the API/MCP page, then fully restart Claude Desktop.

Your token, your control

MCP uses a team API token. Include the mcp:use scope, then grant only the access the client needs. Revoke the token anytime from the API/MCP page.

More articles

Walkthroughs
GoDaddy: Forwarding with HTTPS support
Network Solutions: Forwarding with HTTPS support
Namecheap: Forwarding with HTTPS support
Hover: Forwarding with HTTPS support
TransIP: Forwarding with HTTPS support
Cloudflare: Forwarding with HTTPS support
Amazon Route 53: Forwarding with HTTPS support
NS1: Forwarding with HTTPS support
DigitalOcean: Forwarding with HTTPS support
Google Cloud DNS: Forwarding with HTTPS support
EuroDNS: Forwarding with HTTPS support
Azure DNS: Forwarding with HTTPS support
DNS Made Easy: Forwarding with HTTPS support
Freenom: Forwarding with HTTPS support
Mijndomein: Forwarding with HTTPS support

Can’t find the answer you’re looking for?

24 hours
E-mail us
support@redirect.pizza
Start a chat
Online 9:00 - 21:00 CEST
Phone
Available with Enterprise