Overview
What is Rebrandly MCP Tool (Go)?
Rebrandly MCP Tool (Go) is a lightweight MCP server that exposes a single tool—create_short_link—to shorten long URLs through the Rebrandly API. It is designed for developers who want to integrate short link creation into AI assistants or any MCP-compatible client, such as Claude Desktop.
How to use Rebrandly MCP Tool (Go)?
Build the binary from the provided main.go using Go 1.20+ (go build -o rebrandly-tool main.go), then configure your MCP client to run the executable with the environment variable REBRANDLY_API_KEY set to your Rebrandly API key. In Claude Desktop, add a JSON entry under mcpServers specifying the command path and the API key.
Key features of Rebrandly MCP Tool (Go)
- Single tool
create_short_linkfor URL shortening. - Supports optional workspace ID, custom slug, and title.
- Built in Go, resulting in a single‑binary deployment.
- Configured via standard environment variable for API key.
- Works with any MCP‑compatible client (e.g., Claude Desktop).
Use cases of Rebrandly MCP Tool (Go)
- Generate short links automatically from AI chat prompts.
- Integrate branded URL shortening into custom workflows.
- Create trackable links with optional custom slashtags and titles.
- Enable multi‑workspace accounts to route links to the correct workspace.
FAQ from Rebrandly MCP Tool (Go)
What does the create_short_link tool do?
It takes a long URL (required) and optionally a workspace ID, custom slashtag, and title, then returns a shortened Rebrandly link.
What are the prerequisites to run this server?
You need Go 1.20 or higher to build the binary, a Rebrandly account, and a valid Rebrandly API key.
How do I provide my API key to the server?
Set the environment variable REBRANDLY_API_KEY to your key before running the binary. In Claude Desktop, this is done inside the env object of the MCP server configuration.
What transport does the server use?
The server communicates over stdio, as is typical for MCP tools launched by clients like Claude Desktop.
Are there any known limits or additional dependencies?
The README does not mention any limits beyond the API key requirement. The server has no external dependencies beyond a Go runtime for building and the Rebrandly API access.