Tencent Map

Created By
tencent-mapa year ago
腾讯地图官方 MCP Server
Overview

概述

官方文档

随着各类 AI 大模型的发展,快速推动了产业智能化进程,而 AI 与外部资源的交互,是应用落地的基础支撑。为了应对用户多样性的需求,产生了丰富的外部工具,但是因为各类大模的不同开发标准,也造成了一个工具无法在不同 AI 中运行,额外适配要花费大量精力与成本,介于此,MCP 协议的推出形成了统一规范,使得AI与外工具的结合更为简单高效,促进了 AI 的落地化进程。

在AI应用场景中,与真实世界取得连接,进行个性化推荐(推荐餐厅、酒店、活动、景区等),行程规划,获取实时出行信息等,让 AI 服务于人们现实生活,是很多企业与开发者迫切希望实现的。

对此腾讯位置服务推出基于 MCP 协议的位置服务开发接口,助开发者们快速实现基于地理位置的AI服务。

产品特点

腾讯位置服务 MCP Server 产品特点:

  • 使用更简单:基于MCP(SSE)方式,不必部署本地服务,简单配置即可。
  • 升级更方便:我们会持续进行迭代改进,云端化服务,您无须任何额外操作
  • 大模型更易理解:我们对原始的 JSON 结果进行了语义化的转换,更易于大模型理解

提供能力

包含:地址解析,关键词输入提示,逆地址解析,地点搜索(周边),沿途搜索,POI详情查询,驾车路线规划 - 途经点智能排序,驾车路线规划 - 未来路线规划,公交路线规划,骑行路线规划,步行路线规划,距离矩阵:驾车、步行、骑,IP 定位,天气查询等多个能力,具体参考内容说明。

功能与使用限制

腾讯位置服务 MCP Server 依赖地图 WebServiceAPI 构建,因此受 WebServiceAPI 接口本身限制,需要具备以下相应接口的调用权限和配额方可使用, 相关文档:WebServiceAPI调用限制说明WebServiceAPI入门指南

在用户与智能体对话的过程中,智能体根据对话内容判断是否需要调用外部工具(MCPServer)获取信息来解答用户问题,MCPServer根据智能体提供的参数,会调用对应的WebServiceAPI接口获取结果,智能体理解其中内容,并加以整理最后回复给用户。

智能体可能在这一过程中调用多个 MCP Server 中的工具接口(可能对应多个 WebServiceAPI 接口),因此相关接口都需要具备调用权限和配额。

Tags: location services, map, map service, tencent, location-services

Server Config

{
  "mcpServers": {
    "tencent-map": {
      "url": "https://mcp.map.qq.com/sse?key=<YourKey>"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tencent-map
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago