Skip to main content
Glama
543366565

mcp-china-ecosystem

by 543366565
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP China Ecosystem 🇨🇳

Bridging AI Agents to the Chinese Internet. Search Baidu, explore Bilibili, extract Chinese web content — no API keys required.

A Model Context Protocol (MCP) server that connects AI agents (Claude Desktop, Cursor, Hermes Agent, etc.) to China's internet ecosystem.

Tools

Tool

Description

baidu_search_tool

Search Baidu — China's #1 search engine. Returns titles, URLs, and snippets in Chinese.

bilibili_search_tool

Search Bilibili — China's largest video platform. Returns videos with creator, views, danmaku, likes. Supports sorting by relevance, popularity, date, or danmaku count.

extract_chinese_page_tool

Extract clean text content from Chinese websites (Zhihu, Bilibili, 36Kr, CSDN, Jianshu, etc.). Strips ads and navigation noise.

Related MCP server: MediaCrawler MCP Server

Quick Start

pip install mcp-china-ecosystem

Or from source:

git clone https://github.com/543366565/mcp-china-ecosystem.git
cd mcp-china-ecosystem
pip install -e .

Run

# stdio mode (for Claude Desktop, Cursor, Hermes)
mcp-china-ecosystem

# SSE mode (remote access)
mcp-china-ecosystem --transport sse --host 0.0.0.0 --port 8000

Configure Claude Desktop

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "china-ecosystem": {
      "command": "mcp-china-ecosystem"
    }
  }
}

Features

  • Zero API keys — All services use public interfaces (Bilibili open API, Baidu web scraping)

  • Chinese-optimized — Built for Chinese-language content and Chinese website structures

  • Lightweight — Single dependency (parsel + httpx), no heavy frameworks

  • Fast — Async HTTPX for concurrent requests

Why This Matters

AI agents are great at searching the global web, but China's internet is a walled garden. Baidu, Bilibili, Zhihu, and other Chinese platforms are inaccessible to most MCP tools. This server fills that gap — giving AI agents direct access to the Chinese internet.

License

MIT

Available Tools

3 tools
baidu_search_toolB

搜索百度网页，获取中文互联网的实时信息。适合查找中文网站、新闻、百科、技术文章等。

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions '实时信息' (real-time info) but lacks details on pagination, rate limits, result format, or any destructive/read-only nature. The behavioral description is insufficient.

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 brief (two sentences), front-loaded with the action. It could include more detail without becoming verbose, but it is well-structured and avoids redundancy.

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

Completeness2/5

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

Given no annotations, no parameter explanations, and unknown output schema details (though output schema exists), the description is incomplete. Missing behavioral traits, parameter guidance, and result handling information.

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

Parameters2/5

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

Schema has 2 parameters (query, max_results) with no descriptions (0% coverage). The description does not explain parameter usage, defaults, or constraints. It should compensate but does not, leaving the agent to infer.

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 verb '搜索' (search) and resource '百度网页' (Baidu web pages), with purpose '获取中文互联网的实时信息' (get real-time info from Chinese internet). It distinguishes from siblings: bilibili_search_tool (video) and extract_chinese_page_tool (page extraction).

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 lists suitable use cases: '适合查找中文网站、新闻、百科、技术文章等' (suitable for finding Chinese websites, news, encyclopedia, tech articles), providing context on when to use. However, it does not explicitly state when not to use or offer alternatives.

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

bilibili_search_toolA

搜索B站视频，获取中国最大视频平台的内容。支持按综合、播放量、最新、弹幕排序。返回视频标题、UP主、播放量、弹幕数等。

ParametersJSON Schema
NameRequiredDescriptionDefault
sortNodefault
queryYes
max_resultsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool returns video title, uploader, play count, danmaku count, etc., implying a read-only search operation. However, it does not explicitly state that the tool is non-destructive, nor does it mention any authorization requirements or rate limits.

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 concise (two sentences) and front-loads the purpose. Every sentence adds value: what the tool does, sort options, and return fields. It could be slightly more structured, but overall efficient.

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 tool has an output schema (covering return values) and 3 parameters, the description provides adequate context: target platform, sort options, and return field highlights. It does not address pagination or result limiting, but the max_results parameter and output schema likely cover that.

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 description coverage is 0%, so the description must compensate. It describes valid sort values (comprehensive, play count, newest, danmaku) and implies query is a search term, but does not mention max_results or clarify whether sort values map exactly to the parameter string. Coverage is partial; mores needed for max_results.

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 explicitly states the tool searches Bilibili videos (the target resource) and lists sort options and returned fields. It clearly distinguishes from sibling tools: baidu_search_tool (web search) and extract_chinese_page_tool (page extraction).

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 indicates the tool is for searching Bilibili content and specifies sort options, but lacks explicit guidance on when to use vs. alternatives or when not to use it. Context from sibling names provides some differentiation, but the description itself does not offer direct comparisons.

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

extract_chinese_page_toolA

提取中文网页的正文内容。适合阅读知乎回答、B站专栏、36氪文章、CSDN博客等中文网站。去除广告和导航干扰。

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.1/5.0
Behavior4/5

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

Discloses key behavior of removing ads and navigation interference. With no annotations provided, the description fulfills transparency for a read-like operation, though it could mention if any authentication is needed.

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?

Two sentences efficiently convey purpose, suitable sites, and behavior. No redundant information.

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?

Description covers what the tool does, for which sites, and what it removes. With an output schema present, lack of return value details is acceptable. Could mention that results are in Chinese.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions URLs should be from Chinese web pages, but does not add constraints like required format, encoding, or examples for the 'url' parameter.

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?

Description clearly states the tool extracts main text from Chinese web pages, with specific examples (Zhihu, Bilibili, 36kr, CSDN) that distinguish it from search-focused siblings like baidu_search_tool and bilibili_search_tool.

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?

Explicitly states it is 'suitable for reading' content from Chinese websites, indicating when to use. While it doesn't specify when not to use, the context of siblings suggests it's for extraction rather than searching.

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.

  1. 3 tool updatesv1.0.0
    • First observedbaidu_search_tool
    • First observedbilibili_search_tool
    • First observedextract_chinese_page_tool
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

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinctly different function: web search, video search, and page extraction. No ambiguity in purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (baidu_search_tool, bilibili_search_tool, extract_chinese_page_tool).

Tool Count4/5

Three tools is minimal but covers essential operations for the China ecosystem domain. Slightly thin but not unreasonably so.

Completeness3/5

Missing tools for other major platforms (Weibo, Zhihu, etc.) and common operations like translation or user info. Gaps exist but core search and extraction are present.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MediaCrawler MCP Server

    mcp-service
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to crawl and extract data from Chinese social media platforms like Bilibili, Xiaohongshu, and Douyin. Provides search, content detail retrieval, and creator information tools with persistent browser sessions and QR code login support.
    76
    -

  • chinese-social-mcp

    zhaohongyuziranerran
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to manage and publish content across multiple Chinese social media platforms including Xiaohongshu, Douyin, WeChat, Weibo, Zhihu, and Bilibili.
    -