Baidu Map

Created By
baidu-mapsa year ago
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Overview

what is Baidu Map?

Baidu Map is a core API service that is fully compatible with the MCP protocol, making it the first map service provider in China to support this protocol.

how to use Baidu Map?

To use Baidu Map, you need to create a server-side API key (AK) on the Baidu Map Open Platform and then integrate the API using either Python or Typescript SDKs.

key features of Baidu Map?

  • Provides 8 core API interfaces including geocoding, reverse geocoding, place search, route planning, and weather queries.
  • Supports integration with intelligent assistants that are compatible with the MCP protocol.

use cases of Baidu Map?

  1. Geocoding addresses to coordinates.
  2. Retrieving detailed information about places of interest (POIs).
  3. Planning routes for driving, walking, or public transport.
  4. Querying current weather based on location.

FAQ from Baidu Map?

  • What is the MCP protocol?

The MCP protocol is a standard for integrating various services and tools in a unified manner. More details can be found in the official MCP documentation.

  • Is there a cost to use Baidu Map API?

The usage of Baidu Map API may vary; please check the Baidu Map Open Platform for pricing details.

  • How can I troubleshoot issues with the API?

You can refer to the official documentation or community forums for troubleshooting tips.

Server Config

{
  "mcpServers": {
    "baidu-map": {
      "command": "npx",
      "args": [
        "-y",
        "@baidumap/mcp-server-baidu-map"
      ],
      "env": {
        "BAIDU_MAP_API_KEY": "xxx"
      }
    }
  }
}
Project Info
Featured
Created At
a year ago
Updated At
a year ago
Author Name
baidu-maps
Star
-
Language
-
License
-

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

2 days ago