RedirectBoss

com.redirectbossPublished by redirectboss.comOfficial publisherv1.0.0Updated Oct 24, 2026

Manage hosts, redirects, SSL, and traffic analytics from Claude and other AI assistants.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureData & Analytics

Overview

AI-generated overview

Remote MCP server that lets an AI assistant manage RedirectBoss hosts, redirects, SSL certificates and traffic analytics.

What you can do
  • Manage hosts and their configuration
  • Create and maintain redirect rules
  • Handle SSL certificates for domains
  • Review traffic analytics for hosts and redirects
When to use it
Useful when you run sites or domains through RedirectBoss and want to inspect or adjust redirects, hosts, SSL and traffic stats from an AI assistant instead of the dashboard.
Requirements
Remote streamable HTTP endpoint at mcp.redirectboss.com; an OAuth sign-in to a RedirectBoss account is required. No environment variables or headers are declared.
Before you install
The server can change live hosting configuration: redirect rules, hosts and SSL settings may be created or modified, which can affect production traffic. Access is granted through OAuth to your RedirectBoss account, so review the scopes you approve.

Installation

In SourceWeft

  1. Open RedirectBoss in the dashboard and add it to a workspace.
  2. Connect the required 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/com.redirectboss%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "redirectboss": {
      "type": "http",
      "url": "https://mcp.redirectboss.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

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.