MCP Server

MCP server for URL shortening and management. Exposed over MCP by the mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Create short, shareable URLs directly from Claude, VS Code, or any MCP-compatible client.

• URL Shortening — - Convert long URLs into short, shareable links
• Batch Shortening — - Shorten multiple URLs at once (up to 10 per batch)
• Free Service — - Zero credit consumption per request
• Permanent Links — - Short URLs never expire
• surl.id Domain — - Short URLs use the clean surl.id domain
• Bearer Auth — - Secure API access with token authentication

Its toolset

Everything the assistant can do here goes through one of these:

• Endpoint — POST /shorturl
• Input — { "content": "https://long-url.example.com/..." }
• Output — { "success": true, "data": { "url": "https://surl.id/..." } }
• Pricing — Free (0 credits)
• Auth — Bearer token
• shorturl_create — Shorten a single URL
• shorturl_batch_create — Shorten multiple URLs at once (max 10)
• shorturl_get_usage_guide — Get comprehensive usage guide
• shorturl_get_api_info — Get API details and error codes
• Cline — The Cline tool exposed by this server

Configuration

You will need 5 environment variables: ACEDATACLOUD_API_TOKEN, YOUR_API_TOKEN, ACEDATACLOUD_API_BASE_URL, ACEDATACLOUD_OAUTH_CLIENT_ID, ACEDATACLOUD_PLATFORM_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Endpoint, Input, Output and 7 more — is a fair guide to whether it matches your workflow. It is maintained by AceDataCloud; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.