Rebrandly MCP for AI. Manage branded links and domain assets via API calls.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Rebrandly MCP Server manages your branded short URLs. You can create custom links, organize them across multiple domains, update link metadata programmatically, and pull real-time click stats for campaign tracking.
It's an API layer that gives your AI client full control over your brand's online presence.
What AI agents can do with Rebrandly Automation
Get link count
Checks how many total branded links are currently set up in your workspace.
Create branded link
Shortens a standard URL into a custom, branded slug.
Delete short link
Permanently removes an existing short link from your account.
The agent generates a short, custom URL pointing to any destination.
You can check metadata about your custom domains or list all available ones.
The agent pulls detailed info, including click counts and destination details, for any given link.
You update a link's final URL or its descriptive metadata without recreating the slug.
The agent lists all your branded links, checks how many you have used, or searches for specific titles.
Ask an AI about this
Waiting for input…
What AI agents can do with Rebrandly MCP Server: 12 Tools for Link Management
These tools let your AI client manage the full lifecycle of branded links—from creation and domain checking to metadata updates and analytics retrieval.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Rebrandly on VinkiusGet Link Count
Checks how many total branded links are currently set up in your workspace.
Create Branded Link
Shortens a standard URL into a custom, branded slug.
Delete Short Link
Permanently removes an existing short link from your account.
Get Account Details
Retrieves basic profile information for the connected Rebrandly account.
Get Domain Info
Fetches metadata and status details about a specific custom domain you own.
Get Link Details
Retrieves the full information and statistics for one specific short link.
List Branded Domains
Lists every custom domain name you own and manage within Rebrandly.
List Short Links
Retrieves a list of all branded links in the current workspace.
List Account Workspaces
Shows all separate team environments or workspaces linked to your account.
Search Links By Title
Finds specific short links by searching against their assigned title.
Test Rebrandly Auth
Verifies that your AI client can successfully authenticate and connect to Rebrandly.
Update Link Metadata
Changes the destination URL or metadata of an existing link without changing its slug.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Rebrandly integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Rebrandly, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Rebrandly. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing links and domains shouldn't require juggling multiple tabs., Solved with Vinkius AI Gateway
Today, updating a branded URL means jumping between the main link dashboard, the custom domain settings page, and then finding the specific asset in a list. You copy the old slug, paste it into a form, confirm the destination URL, and hope you didn't miss checking if the associated domain was still paid up.
With Rebrandly MCP Server, your agent handles this whole process. Tell it: 'Update link X to point here.' It checks the domains, confirms ownership via `get_domain_info`, and executes the change using `update_link_metadata`. You get a confirmation status—that's all.
Rebrandly MCP Server: Control your link assets with API calls.
The manual steps that disappear are the repetitive checks. No more logging into the site just to count links; use `get_link_count`. No more guessing if a domain is active—just call `list_branded_domains` and check the metadata. Everything is exposed.
Now, link management is a data operation. You treat your branded URLs like any other asset: read, write, delete, or analyze. The control you gain shifts your focus from clicking buttons to refining strategy.
What your AI can actually do with this
The Rebrandly MCP Server gives your AI client total control over your branded URLs and domains. You don't have to mess with the web dashboard; you just tell your agent what needs doing, and it handles everything through our tools.
Testing and Setup
First off, you'll run test_rebrandly_auth to make sure your client can actually talk to Rebrandly. After that, if you need basic account context, the agent pulls profile information using get_account_details. If you're working with multiple teams, it lists all available environments or workspaces via list_account_workspaces. You also get a simple count of how many branded links are set up across your entire workspace by calling get_link_count.
Domain Management
You own several custom domains for branding, and the server manages them. To see every single domain name you control, run list_branded_domains. If you need to know the specific status or technical details of one particular domain—like its metadata—the agent fetches that data with get_domain_info. This lets your client verify if a domain is set up correctly before using it.
Creating and Updating Links
Need a new custom link? The agent shortens any standard URL into a unique, branded slug using create_branded_link. You can't just create and forget it, though. If you need to change the final destination URL or update descriptive metadata for an existing link without changing its actual branded slug, use update_link_metadata.
This is key because it lets you pivot your marketing strategy on the fly. Finally, if a link is retired, the agent permanently deletes it using delete_short_link.
Monitoring and Searching Assets
The server gives you several ways to check what links you've deployed. To get an overall roster of every branded link in the current workspace, the client runs list_short_links. If you know part of the title assigned to a link, the agent searches specifically using search_links_by_title to pinpoint it.
For deep performance analysis, calling get_link_details pulls everything—the full information, destination details, and real-time click statistics for that specific slug. You can also view all the detailed stats for any existing link by running this same tool.
Summary of Control
You've got comprehensive control over your entire online presence with these tools. The client checks basic account data (get_account_details), verifies authentication (test_rebrandly_auth), and manages multiple team workspaces (list_account_workspaces). You can check domain health (get_domain_info) and list all owned domains (list_branded_domains). When it comes to links, you can create them (create_branded_link), update their backend settings without touching the slug name (update_link_metadata), find them by title (search_links_by_title), get a full overview of everything deployed (list_short_links), check the total count (get_link_count), and pull detailed performance data, including click counts, using get_link_details.
Don't forget you can always clean up old assets with delete_short_link.
019dd148-aa60-7158-a7d2-f6f8829f47e3 
Here's how it actually works
The bottom line is, your agent sends a command to Rebrandly via MCP, and this server executes it using the appropriate API tool.
First, the AI client uses test_rebrandly_auth to confirm the connection and get necessary credentials.
Next, it calls a management tool (like create_branded_link) using specific parameters—the target URL and desired slug—to perform an action.
Finally, the server returns status codes and data payloads, confirming if the link was created, updated, or deleted.
Who is this actually for?
This is for brand managers and marketing developers who are sick of clicking through dashboards just to track links or update a campaign URL. If your job involves making sure every link looks exactly right and tracking performance across multiple campaigns, you need this. It lets your agent handle the entire lifecycle.
Uses create_branded_link to rapidly launch new campaign links with custom slugs for specific product lines.
Runs list operations (list_short_links) and uses update_link_metadata to ensure all archived links still point to the correct, current marketing landing page.
Integrates API calls for bulk link management or checks domain status using get_domain_info before deployment.
What Changes When You Connect
Create custom slugs instantly. Use create_branded_link to launch new, trackable URLs for every campaign phase. No more generic bit.ly links—you own the brand slug.
Keep your domains organized. You can use list_branded_domains and get_domain_info to see exactly which custom domains are active, ensuring no marketing efforts point to a stale or unverified domain.
Adapt campaigns on the fly. Instead of having to recreate a link when a landing page changes, just run update_link_metadata. The slug stays; the destination updates.
Check performance fast. Use get_link_details and list_short_links to pull immediate click stats or find exactly which links are underperforming without building complex reports.
Audit your setup easily. Run list_account_workspaces if you manage multiple teams, keeping link assets separated and controlled within specific team environments.
See it in action
The expiring campaign link
A product manager needs to update a link for an old summer sale. Instead of logging into the dashboard, they ask their agent: 'Find the link titled 'Summer Sale 2024' and change its destination URL to our new evergreen page.' The agent runs search_links_by_title then uses update_link_metadata, solving it in two steps.
New product launch requiring custom domains
The dev team needs a branded link structure for a new B2B service. They first use list_branded_domains to confirm the available custom TLDs, then use create_branded_link multiple times with specific slugs and domain identifiers.
Mass cleanup of old assets
A brand manager is retiring a product line. They ask their agent to list all links associated with that line using list_short_links, then send the full list to be deleted via delete_short_link to prevent confusion.
Checking account boundaries
A team needs to know if another department has created links in their space. They first use list_account_workspaces and then scope down using tools like get_link_count within the correct workspace ID.
The honest tradeoffs
Treating link creation as a one-off event
The user manually copies the destination URL, then pastes it into the dashboard. They forget to check if the domain is active or if they need to update any associated metadata.
Always use get_domain_info first to verify your custom domain status. Then, run create_branded_link, making sure you pass all necessary metadata parameters in one go.
Updating links manually after a migration
After moving the primary landing page, someone remembers they need to change the URL but can't find the link ID or title. They waste time clicking through multiple list views.
Use search_links_by_title to locate the asset quickly, and then use update_link_metadata to modify the destination URL programmatically.
Trying to manage links without scope
A developer runs a simple link count query that returns an inaccurate number because they forgot to specify which team workspace the links belong to.
Always call list_account_workspaces first. This confirms all available environments, allowing you to correctly target your management tools within the right scope.
When It Fits, When It Doesn't
Use this MCP Server if link management is a core, automated part of your workflow—specifically if you need to create, list, or modify hundreds of branded links across multiple domains. This is for structured asset control.
Don't use it if you just need to share one-off links quickly; the dashboard works fine then. Also, don't use this if your main problem is simply analyzing why a link failed—you might only need basic reporting tools instead of full CRUD access.
If you are constantly asking: 'How do I change X and check Y?', run these tools in sequence: get_link_details (to read the current state), then decide if you need to use update_link_metadata or delete_short_link. If the link structure itself is wrong, start with list_branded_domains to fix domain ownership first.
Questions you might have
How do I check if my custom domain is valid using Rebrandly MCP Server? +
You use the get_domain_info tool. This function pulls metadata about your specific branded domain, confirming its status and helping you verify it's ready to be used for links.
What is the best way to update a link’s destination URL? +
Use update_link_metadata. This tool lets you change the final target URL or modify other metadata fields of an existing short link without having to recreate the entire branded slug.
Can I see all my links across different client teams? +
Yes. First, run list_account_workspaces to get a list of all team environments. Then, you can use tools like list_short_links scoped to the specific workspace ID.
How do I find a link if I don't know its slug? +
Use search_links_by_title. This tool lets you search for links based on their assigned title, which is much easier than trying to remember the exact branded slug.
Rebrandly MCP Server, how do I check if my API credentials are working correctly? +
You run the test_rebrandly_auth tool. This confirms that your provided API Key and Workspace ID are active and formatted correctly for immediate agent use.
Using Rebrandly MCP Server, what is the proper way to delete a branded short link? +
Call delete_short_link with the specific URL or ID. Your agent sends a direct API call that removes the branded link from your account immediately.
With Rebrandly MCP Server, how can I check my current usage limits for branded links? +
Use get_link_count to see the total number of links you've generated. This metric helps you track your link consumption against plan capacity.
Rebrandly MCP Server, how do I list all the custom domains registered under my account? +
Run the list_branded_domains tool. It returns a full roster of every custom domain name associated with your Rebrandly account for review.
What is a slashtag? +
A slashtag is the custom alias that comes after the domain in a short link (e.g., rebrand.ly/myslash).
Can I track clicks via API? +
Yes, every link object returned by the API includes a 'clicks' property with the total number of visits.
We've already built the connector for Rebrandly. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.