Bring Url Shortener
to Cursor
Learn how to connect AB.GL to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the AB.GL MCP Server?
Connect your AB.GL account to any AI agent and manage your entire link shortening and analytics workflow through natural conversation.
What you can do
- Create Short Links — Shorten any URL with an optional custom alias for branded campaigns
- Link Management — List, inspect, update, and delete shortened URLs from your account
- Click Analytics — View detailed click statistics including referrers, devices, and geographic data for any link
- Bio Link Pages — List and inspect bio link pages with blocks and appearance settings
- Custom Domains — View all custom domains configured for your short links
- Account Monitoring — Verify API connectivity and account status
How it works
1. Subscribe to this server
2. Enter your API Key from your AB.GL account settings
3. Start managing links from Claude, Cursor, or any MCP client
Who is this for?
- Marketing Teams — create branded short links and track campaign performance in real time
- Content Creators — manage bio link pages and monitor audience engagement
- Growth Engineers — automate link creation for A/B testing and attribution tracking
Built-in capabilities (10)
Verify API connectivity
gl. Create a short link
Delete a short link
Get bio page details
Get link details
Get link analytics
List bio pages
gl short links. List custom domains
gl account with click counts and creation dates. List all short links
Update a short link
Why Cursor?
Cursor's Agent mode turns AB.GL into an in-editor superpower. Ask Cursor to generate code using live data from AB.GL and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
AB.GL in Cursor
AB.GL and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect AB.GL to Cursor 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 AB.GL in Cursor
The AB.GL 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 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
AB.GL for Cursor
Every tool call from Cursor to the AB.GL MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI create branded short links with custom aliases?
Yes. Use the create_short_link tool with the URL and an optional alias parameter. For example, ask your agent to shorten 'example.com/campaign' with alias 'summer24'.
How do I view click analytics for a specific link?
Use the get_link_stats tool with the link ID. The agent returns total clicks, referrer sources, device breakdown, and geographic distribution.
Can I manage and delete links through the AI?
Yes. The update_link tool changes the destination URL of an existing link, and delete_link permanently removes it from your account. Both require the link ID.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.