redirect.pizza

pizza.redirectPublished by redirect.pizzaOfficial publisherv1.0.0Updated Oct 24, 2026

Manage URL redirects, domains, email forwards, and analytics on redirect.pizza.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage URL redirects, domains, email forwards, and analytics on a redirect.pizza account.

What you can do
This is a remote MCP server for the redirect.pizza service. According to the registry description, it lets an assistant manage URL redirects, domains, email forwards, and analytics on a redirect.pizza account. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Useful when you already run redirects, custom domains, or email forwarding through redirect.pizza and want an assistant to help manage them or review their analytics from a chat session.
Requirements
A remote endpoint at redirect.pizza over streamable HTTP. A redirect.pizza account and a Team API token are required, sent as a bearer token in the Authorization header.
Before you install
The server requires a Team API token sent in the Authorization header; treat it as a secret and grant only the access you need. Managing redirects, domains, and email forwards can change or remove live routing, so review changes before they take effect.

Installation

In SourceWeft

  1. Open redirect.pizza in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/pizza.redirect%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "redirect-pizza": {
      "type": "http",
      "url": "https://redirect.pizza/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Redirect integrations