Bring Link Shortener
to VS Code Copilot
Learn how to connect Rebrandly to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Rebrandly MCP Server?
What you can do
- Create and manage branded short links with custom slashtags to enhance your brand presence and track performance.
- Organize your links across different workspaces and domains to maintain a structured marketing ecosystem.
- Update destination URLs, titles, and metadata programmatically to adapt to changing marketing campaigns.
- Access real-time click statistics and account metadata through the Rebrandly REST API v1.
How it works
1. Retrieve your API Key from your Rebrandly account (Account > API). 2. Optionally provide a Workspace ID to manage links within specific team environments. 3. Connect your AI agent to automate link generation, campaign tracking, and branding workflows.Who is it for?
Designed for digital marketers, brand managers, and developers who want to leverage AI for intelligent link management and high-fidelity branding automation.Built-in capabilities (12)
Shorten a URL
Remove a link
Get profile info
Get domain metadata
Check link usage
Get link info
List team spaces
List custom domains
List branded links
Find links
Check connection
Modify a link
Why VS Code Copilot?
GitHub Copilot Agent mode brings Rebrandly data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Rebrandly in VS Code Copilot
Rebrandly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Rebrandly to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Rebrandly in VS Code Copilot
The Rebrandly MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Rebrandly for VS Code Copilot
Every tool call from VS Code Copilot to the Rebrandly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.