Antalya Transfers

co.antalyatransfers由 antalyatransfers.co 发布官方发布者v1.0.0更新于 Oct 25, 2026

Quote and request private airport transfers in Antalya, Turkey. Operator confirms each request.

已验证Streamable HTTP可网页运行位置与生活商业与电商

概览

AI 生成的概览

一个用于土耳其安塔利亚私人机场接送报价与提交请求的 MCP 服务器,每笔请求由运营商确认。

可以做什么
获取安塔利亚机场与周边度假地之间私人接送的欧元固定价格报价,含车型适配与价格信息。在客户选定路线、时间和车型并提供联系方式后提交接送请求。凭预订编号和邮箱查询请求是待确认、已确认、已分配还是已取消。取消待确认或已分配的请求,并通知运营商和客户。
适用场景
适合助手协助旅客规划安塔利亚机场接送、需要实时价格或将预订请求转交运营商时使用。请求由运营商审核确认,并非即时完成预订。
运行要求
远程 MCP 端点;未声明本地运行时、软件包、账户或 API 密钥。提交请求需要客户姓名、邮箱和电话;查询或取消需要预订编号和邮箱。
安装前请注意
提交请求会把客户姓名、邮箱和电话发送给第三方运营商,运营商通过邮件或 WhatsApp 确认行程和最终价格。请求以待确认状态保存,报价或提交都不等于已确认预订。取消会改变请求状态并通知运营商和客户,仅在客户明确要求时操作。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Antalya Transfers,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/co.antalyatransfers%2Ftransfers/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "antalya-transfers": {
      "type": "http",
      "url": "https://api.antalyatransfers.co/api/mcp"
    }
  }
}

工具

4

get_price_quote

Get airport transfer price quote

Use this when a traveller asks how much a private airport transfer costs between Antalya Airport (AYT) and Antalya-area destinations (Konyaaltı, Antalya city/Kaleiçi, Lara, Belek, Side, Alanya, Kemer, Kaş) or between those resorts. Returns a fixed-price estimate in EUR, whether the party fits the chosen vehicle, and a suggested vehicle if not. Read-only: it does not create a request or reserve anything. Do not use for flights, car rental, tours, or destinations outside the Antalya region. If a route has no fixed price, priced=false and the operator quotes it.

输入参数luggagechildSeatspassengers必填scheduledAtvehicleTypepickupAddress必填dropoffAddress必填

create_transfer_request

Submit transfer request (pending operator confirmation)

Use this only after the customer has chosen a route, time and vehicle and has given their name, email and phone, and explicitly asked to send the request. Submits a transfer REQUEST that is stored as pending and reviewed by the operator, who confirms the ride and final price by email/WhatsApp. This does NOT confirm a booking, assign a driver or take payment — never tell the customer the ride is confirmed. Writes data: do not call it to explore prices (use get_price_quote) and do not retry on success. Pass idempotencyKey to make retries safe: the same key for the same customer returns the original reference (duplicate=true) and never creates a second request; to change details, cancel and submit a new request with a new key. Without a key, repeating identical details also returns the original request. At most 5 requests per phone number per day. Capacity is checked: parties larger than the vehicle are rejected with a suggested vehicle.

输入参数petsnotesluggagelanguagechildSeatspassengers必填scheduledAt必填vehicleType必填customerName必填flightNumbercustomerEmail必填customerPhone必填另有 3 个

get_request_status

Check transfer request status

Use this when the customer asks whether their transfer request was confirmed, assigned or cancelled. Requires the booking reference returned by create_transfer_request and the email used for the request. Read-only. pending means the operator has not confirmed yet; only operatorConfirmed=true means the ride is confirmed. Do not use to create or change a request.

输入参数reference必填customerEmail必填

cancel_transfer_request

Cancel a pending transfer request

Use this only when the customer has explicitly asked to cancel their transfer request and you have the booking reference returned by create_transfer_request and the email used for it. Cancels a request that is still pending or assigned, tells the operator (WhatsApp/email) and emails the customer a cancellation notice. Calling it again for an already-cancelled request is harmless and returns cancelled=true without notifying anyone again. Destructive and sends real messages: never call it to explore, to "test", or because the customer is merely unsure or wants to change details. Do not use for a request the operator has already confirmed (it is refused: the customer must contact the operator), for changing time/passengers/vehicle (contact the operator), or for refunds. Use get_request_status to check the current state first if unsure.

输入参数reasonreference必填customerEmail必填

版本历史

1
  1. v1.0.0最新Oct 13, 2026

评分

已满足适用检查项的 72%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分

    请在注册中心条目中发布图标。

  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。