de en es ja ko ru zh

ShortURLMCP

Name: ShortURLMCP
Author: AceDataCloud

by AceDataCloud

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

ShortURLMCP

PyPI version PyPI downloads Python 3.10+ License: MIT MCP

一个用于 URL 缩短的 Model Context Protocol (MCP) 服务器，通过 AceDataCloud API 使用 Short URL API。

直接从 Claude、VS Code 或任何兼容 MCP 的客户端创建简短、可共享的 URL。

功能特性

URL 缩短 - 将长 URL 转换为简短、可共享的链接
批量缩短 - 一次缩短多个 URL（每批最多 10 个）
免费服务 - 每次请求零积分消耗
永久链接 - 短链接永不过期
surl.id 域名 - 短链接使用简洁的 surl.id 域名
Bearer 认证 - 通过令牌认证实现安全的 API 访问

Related MCP server: shrtnr MCP Server

工具参考

工具	描述
`shorturl_create`	从长 URL 创建短 URL。
`shorturl_batch_create`	在单个批次中为多个长 URL 创建短 URL。
`shorturl_get_usage_guide`	获取使用 ShortURL 工具的综合指南。
`shorturl_get_api_info`	获取有关 ShortURL API 服务的信息。

快速入门

1. 获取您的 API 令牌

在 AceDataCloud 平台注册
前往 API 文档页面
点击 “Acquire” 获取您的 API 令牌
复制令牌以供下方使用

2. 使用托管服务器（推荐）

AceDataCloud 托管了一个受管理的 MCP 服务器 —— 无需本地安装。

端点： https://shorturl.mcp.acedata.cloud/mcp

所有请求都需要 Bearer 令牌。请使用第 1 步中的 API 令牌。

Claude.ai

通过 OAuth 直接在 Claude.ai 上连接 —— 无需 API 令牌：

前往 Claude.ai 设置 → 集成 → 添加更多
输入服务器 URL：https://shorturl.mcp.acedata.cloud/mcp
完成 OAuth 登录流程
开始在对话中使用这些工具

Claude Desktop

添加到您的配置中（macOS 上为 ~/Library/Application Support/Claude/claude_desktop_config.json）：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Cursor / Windsurf

添加到您的 MCP 配置（.cursor/mcp.json 或 .windsurf/mcp.json）：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

VS Code (Copilot)

添加到您的 VS Code MCP 配置（.vscode/mcp.json）：

{
  "servers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

或者为 VS Code 安装 Ace Data Cloud MCP 扩展，该扩展捆绑了所有 15 个 MCP 服务器，支持一键设置。

JetBrains IDEs

前往 设置 → 工具 → AI Assistant → Model Context Protocol (MCP)
点击添加 → HTTP
粘贴：

{
  "mcpServers": {
    "shorturl": {
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Claude Code

Claude Code 原生支持 MCP 服务器：

claude mcp add shorturl --transport http https://shorturl.mcp.acedata.cloud/mcp \
  -h "Authorization: Bearer YOUR_API_TOKEN"

或者添加到您项目的 .mcp.json 中：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Cline

添加到 Cline 的 MCP 设置（.cline/mcp_settings.json）：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Amazon Q Developer

添加到您的 MCP 配置：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Roo Code

添加到 Roo Code MCP 设置：

{
  "mcpServers": {
    "shorturl": {
      "type": "streamable-http",
      "url": "https://shorturl.mcp.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Continue.dev

添加到 .continue/config.yaml：

mcpServers:
  - name: shorturl
    type: streamable-http
    url: https://shorturl.mcp.acedata.cloud/mcp
    headers:
      Authorization: "Bearer YOUR_API_TOKEN"

Zed

添加到 Zed 的设置（~/.config/zed/settings.json）：

{
  "language_models": {
    "mcp_servers": {
      "shorturl": {
        "url": "https://shorturl.mcp.acedata.cloud/mcp",
        "headers": {
          "Authorization": "Bearer YOUR_API_TOKEN"
        }
      }
    }
  }
}

cURL 测试

# Health check (no auth required)
curl https://shorturl.mcp.acedata.cloud/health

# MCP initialize
curl -X POST https://shorturl.mcp.acedata.cloud/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'

3. 或在本地运行（替代方案）

如果您更喜欢在自己的机器上运行服务器：

# Install from PyPI
pip install mcp-shorturl
# or
uvx mcp-shorturl

# Set your API token
export ACEDATACLOUD_API_TOKEN="your_token_here"

# Run (stdio mode for Claude Desktop / local clients)
mcp-shorturl

# Run (HTTP mode for remote access)
mcp-shorturl --transport http --port 8000

Claude Desktop (本地)

{
  "mcpServers": {
    "shorturl": {
      "command": "uvx",
      "args": ["mcp-shorturl"],
      "env": {
        "ACEDATACLOUD_API_TOKEN": "your_token_here"
      }
    }
  }
}

Docker (自托管)

docker pull ghcr.io/acedatacloud/mcp-shorturl:latest
docker run -p 8000:8000 ghcr.io/acedatacloud/mcp-shorturl:latest

客户端使用各自的 Bearer 令牌进行连接 —— 服务器会从每个请求的 Authorization 标头中提取令牌。

可用工具

URL 缩短工具

工具	描述
`shorturl_create`	缩短单个 URL
`shorturl_batch_create`	一次缩短多个 URL（最多 10 个）

信息工具

工具	描述
`shorturl_get_usage_guide`	获取综合使用指南
`shorturl_get_api_info`	获取 API 详情和错误代码

使用示例

缩短单个 URL

User: Shorten this URL: https://platform.acedata.cloud/documents/a2303356-6672-4eb8-9778-75f55c998fe9

Claude: I'll shorten that URL for you.
[Calls shorturl_create with url="https://platform.acedata.cloud/documents/a2303356-6672-4eb8-9778-75f55c998fe9"]

Result: https://surl.id/1uHCs01xa5

批量缩短多个 URL

User: Shorten these URLs for my social media posts:
- https://example.com/blog/very-long-article-title-about-ai
- https://example.com/products/new-release-2024

Claude: I'll shorten both URLs at once.
[Calls shorturl_batch_create with urls=[...]]

为文档创建链接

User: I need clean short links for these reference URLs in my doc.

Claude: I'll create short links for all your references.
[Calls shorturl_batch_create with the list of URLs]

响应结构

成功响应

{
  "success": true,
  "data": {
    "url": "https://surl.id/1uHCs01xa5"
  }
}

错误响应

{
  "success": false,
  "error": {
    "code": "api_error",
    "message": "fetch failed"
  },
  "trace_id": "2cf86e86-22a4-46e1-ac2f-032c0f2a4e89"
}

配置

环境变量

变量	描述	默认值
`ACEDATACLOUD_API_TOKEN`	来自 AceDataCloud 的 API 令牌	必需
`ACEDATACLOUD_API_BASE_URL`	API 基础 URL	`https://api.acedata.cloud`
`ACEDATACLOUD_OAUTH_CLIENT_ID`	OAuth 客户端 ID（托管模式）	—
`ACEDATACLOUD_PLATFORM_BASE_URL`	平台基础 URL	`https://platform.acedata.cloud`
`SHORTURL_REQUEST_TIMEOUT`	请求超时（秒）	`30`
`LOG_LEVEL`	日志级别	`INFO`

命令行选项

mcp-shorturl --help

Options:
  --version          Show version
  --transport        Transport mode: stdio (default) or http
  --port             Port for HTTP transport (default: 8000)

开发

设置开发环境

# Clone repository
git clone https://github.com/AceDataCloud/ShortURLMCP.git
cd ShortURLMCP

# Create virtual environment
python -m venv .venv
source .venv/bin/activate  # or `.venv\Scripts\activate` on Windows

# Install with dev dependencies
pip install -e ".[dev,test]"

运行测试

# Run unit tests
pytest

# Run with coverage
pytest --cov=core --cov=tools

# Run integration tests (requires API token)
pytest tests/test_integration.py -m integration

代码质量

# Format code
ruff format .

# Lint code
ruff check .

# Type check
mypy core tools

构建与发布

# Install build dependencies
pip install -e ".[release]"

# Build package
python -m build

# Upload to PyPI
twine upload dist/*

项目结构

ShortURLMCP/
├── core/                   # Core modules
│   ├── __init__.py
│   ├── client.py          # HTTP client for ShortURL API
│   ├── config.py          # Configuration management
│   ├── exceptions.py      # Custom exceptions
│   └── server.py          # MCP server initialization
├── tools/                  # MCP tool definitions
│   ├── __init__.py
│   ├── shorturl_tools.py  # URL shortening tools
│   └── info_tools.py      # Information tools
├── prompts/                # MCP prompt templates
│   └── __init__.py
├── tests/                  # Test suite
│   ├── conftest.py
│   ├── test_client.py
│   ├── test_config.py
│   └── test_integration.py
├── deploy/                 # Deployment configs
│   ├── run.sh
│   └── production/
│       ├── deployment.yaml
│       ├── ingress.yaml
│       └── service.yaml
├── .env.example           # Environment template
├── .gitignore
├── .ruff.toml             # Ruff linter configuration
├── CHANGELOG.md
├── Dockerfile             # Docker image for HTTP mode
├── docker-compose.yaml    # Docker Compose config
├── LICENSE
├── main.py                # Entry point
├── pyproject.toml         # Project configuration
└── README.md

API 参考

此服务器封装了 AceDataCloud 短 URL API：

端点: POST /shorturl
输入: { "content": "https://long-url.example.com/..." }
输出: { "success": true, "data": { "url": "https://surl.id/..." } }
定价: 免费（0 积分）
认证: Bearer 令牌

完整 API 文档：AceDataCloud 平台

许可证

MIT 许可证 - 详情请参阅 LICENSE。

Available Tools

4 tools

shorturl_batch_createAInspect

Create short URLs for multiple long URLs in a single batch.

Shortens multiple URLs at once, returning a mapping of original URLs
to their shortened versions. Useful for bulk URL shortening tasks.

Args:
    urls: A list of long URLs to shorten (max 10 per batch).

Returns:
    JSON response containing the mapping of original to shortened URLs.

Example:
    shorturl_batch_create(urls=["https://example.com/long-url-1", "https://example.com/long-url-2"])

ParametersJSON Schema

Name	Required	Description	Default
`urls`	Yes	A list of long URLs to shorten. Each must be a valid HTTP or HTTPS URL. Maximum 10 URLs per batch.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description provides key behavioral details: it returns a mapping of original to shortened URLs, handles multiple URLs, and enforces a maximum of 10 per batch. It does not mention error handling or idempotency, but covers the core behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at about 6 sentences, well-structured with a title, explanation, args, returns, and an example. No wasted words, and all sentences are informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and only one parameter, the description fully covers the tool's purpose, usage constraints, and provides an example. It is complete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description repeats the constraint of 'max 10 per batch' which is already in the schema description, thus adds no new meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates short URLs for multiple long URLs in a single batch, which distinguishes it from the sibling tool shorturl_create that likely handles a single URL. The verb 'Create' and resource 'short URLs' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'useful for bulk URL shortening tasks,' which implies when to use this tool over alternatives. However, it does not explicitly state when not to use it or name alternatives like shorturl_create for single URLs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

shorturl_createAInspect

Create a short URL from a long URL.

Converts a long URL into a short, easy-to-share URL using the ShortURL API.
The short URL redirects to the original long URL when visited.

This is useful for:
- Sharing links on social media with character limits
- Creating clean, memorable links for marketing
- Tracking link clicks and engagement
- Making long URLs more manageable in documents and messages

Args:
    url: The long URL to shorten. Must be a valid HTTP or HTTPS URL.

Returns:
    JSON response containing the shortened URL.

Example:
    shorturl_create(url="https://platform.acedata.cloud/documents/a2303356-6672-4eb8-9778-75f55c998fe9")

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes	The long URL to shorten. Must be a valid HTTP or HTTPS URL. Required.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description only mentions conversion and redirection. Lacks details on rate limits, authentication, costs, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with bullet points and example. Front-loaded with main action. Some redundancy but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with output schema but description vague on return structure. Lacks error handling or validation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% with clear parameter description. Description adds examples but no additional meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Create a short URL from a long URL' with specific verb and resource. Distinguishes from siblings like batch_create, get_api_info, get_usage_guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Lists use cases (social media, marketing, tracking, documents) but does not explicitly state when not to use or compare to batch_create.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

shorturl_get_api_infoAInspect

Get information about the ShortURL API service.

Returns details about the API endpoint, pricing, and service capabilities.

Returns:
    API information and service details.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions it returns API information and service details but does not disclose side effects, authentication needs, or rate limits. For a simple info tool, it is minimally adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a returns line. It is concise but slightly redundant repeating 'Returns:' line. Not verbose, but could be more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and an output schema present, the description gives adequate info about returns. However, it lacks context on authentication or how it differs from shorturl_get_usage_guide, making it just adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is 100%. The description adds value by explaining what information is returned (API endpoint, pricing, capabilities), which goes beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets information about the ShortURL API service, including endpoint, pricing, and capabilities. It distinguishes from siblings: shorturl_batch_create and shorturl_create are for creating URLs, shorturl_get_usage_guide is about usage guide, not API info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like shorturl_get_usage_guide. Usage is implied but no exclusion or guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

shorturl_get_usage_guideAInspect

Get a comprehensive guide for using the ShortURL tools.

Provides detailed information on how to use the ShortURL tools
effectively, including parameters, examples, and best practices.

Returns:
    Complete usage guide for ShortURL tools.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the tool returns a guide but does not disclose read-only behavior, side effects, authentication requirements, or rate limits. The description is minimal on behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and to the point, with two brief paragraphs and a Returns line. There is minor repetition of 'ShortURL tools', but overall it is efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool (a guide retriever) and the presence of an output schema (though not visible), the description covers the main purpose and return value. It could mention the format of the guide, but it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the description does not need to add parameter-level meaning. Schema coverage is 100% (0 params), and the baseline for no parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool retrieves a comprehensive guide for using ShortURL tools. It uses a specific verb ('Get') and resource ('usage guide'), and this purpose is distinct from sibling tools like shorturl_create or shorturl_get_api_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when one needs to learn how to use ShortURL tools effectively, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., shorturl_get_api_info) or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv0.1.29May 31, 2026
- Addedshorturl_batch_create
- Addedshorturl_create
- Addedshorturl_get_api_info
- Addedshorturl_get_usage_guide
4 tool updatesv0.1.28May 24, 2026
- Removedshorturl_batch_create
- Removedshorturl_create
- Removedshorturl_get_api_info
- Removedshorturl_get_usage_guide

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored 2026-05-31 21:30 across 4 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: single create, batch create, API info, and usage guide. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent 'shorturl_' prefix with verb_noun pattern (e.g., batch_create, get_api_info). Perfectly uniform.

Tool Count5/5

With 4 tools, the server is well-scoped for a URL shortening service. It covers the core operations (create, batch create) and supporting info tools.

Completeness4/5

Covers all essential creation and information needs. Minor gap: no delete or update functionality, but agents can manage by creating new short URLs.

Maintenance

ActivityMaintained

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Related MCP Connectors

inbio A
io.github.www-in-bio
Official in.bio MCP server: shorten URLs, styled QR codes, and click analytics. No API key needed.
Marketing Data Visualization
122
Razi Web Tools A
io.github.razikallayi
Web and URL utilities over MCP: shorten URLs, screenshot pages, read page metadata, encode URLs.
Browser Automation Web Scraping
61
artidrop A
ai.artidrop
Publish HTML, Markdown, and multi-file sites as shareable URLs instantly via MCP.
Content Management Systems Developer Tools
42
PicSee Short Link A
io.picsee
Official PicSee MCP server for short links, link management, click analytics, and optional OAuth.
Marketing Social Media
12

Related MCP Servers

URL Shortener MCP
App Automation Developer Tools
Talismanic
A
license
B
quality
D
maintenance
Provides a simple tool to shorten URLs using the CleanURI API, designed to run as a FastMCP server that can be integrated with agent or tool-based systems.
Updated a year ago (2025-07-06 19:06 UTC)
1
4
Apache 2.0
shrtnr MCP Server
Developer Tools
oddbit
A
license
Not graded
quality
A
maintenance
Enables AI assistants to create and manage short URLs via the MCP protocol, with OAuth authentication through Cloudflare Access.
Updated a day ago (2026-09-23 09:23 UTC)
28
Apache 2.0
lnkifyofficial
Developer Tools App Automation
lnkify
A
license
Not graded
quality
D
maintenance
MCP server that enables AI agents to manage Lnkify links, domains, API keys, and analytics. Allows creation and resolution of short links through natural language.
Updated 3 months ago (2026-06-29 15:56 UTC)
MIT
INBIO MCP Serverofficial
Marketing
getinbio
A
license
Not graded
quality
C
maintenance
Official MCP server for INBIO's URL shortener with click analytics and customizable QR codes. Enables link shortening, QR code generation, and link management with optional authentication for advanced features.
Updated 2 months ago (2026-07-23 16:20 UTC)
MIT

ShortURLMCP

功能特性

工具参考

快速入门

1. 获取您的 API 令牌

2. 使用托管服务器（推荐）

Claude.ai

Claude Desktop

Cursor / Windsurf

VS Code (Copilot)

JetBrains IDEs

Claude Code

Cline

Amazon Q Developer

Roo Code

Continue.dev

Zed

cURL 测试

3. 或在本地运行（替代方案）

Claude Desktop (本地)

Docker (自托管)

可用工具

URL 缩短工具

信息工具

使用示例

缩短单个 URL

批量缩短多个 URL

为文档创建链接

响应结构

成功响应

错误响应

配置

环境变量

命令行选项

开发

设置开发环境

运行测试

代码质量

构建与发布

项目结构

API 参考

许可证

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

URL Shortener MCP

shrtnr MCP Server

lnkifyofficial

INBIO MCP Serverofficial