Skip to main content
Glama
Zzzccs123

Baike-Render

by Zzzccs123
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

MCP-Baike-Render

MCP-Baike-Render 是一个用于访问和渲染百度百科内容的 MCP Server。它提供了两个主要功能：

  1. 通过 request_baike 工具获取百度百科讨论数据

  2. 通过 render_baike 提示模板将结构化数据渲染为易读的分析内容

安装

# 安装依赖
npm install

# 构建项目
npm run build

Related MCP server: Wikipedia MCP Server

环境变量配置

复制 .env.example 文件并重命名为 .env，然后根据需要修改其中的配置。

# 百度百科API配置
BAIKE_API_BASE_URL=https://baike.baidu.com/api   # 百度百科API基础URL
BAIKE_DISCUSSION_API=/discussion/gettashuos      # 百度百科讨论API路径
DEFAULT_LEMMA_ID=65258669                        # 默认词条ID（当无法解析提供的URL时使用）
BAIKE_COOKIE=''                                  # 百度百科Cookie，用于API认证和访问限制绕过

# 应用信息
MCP_SERVER_NAME=Baike-Render
MCP_SERVER_VERSION=1.0.0
MCP_SERVER_DESCRIPTION=百度百科内容访问和渲染服务

Cookie配置说明

BAIKE_COOKIE 环境变量用于存储百度百科的Cookie信息，这对于获取某些受限内容或防止请求被限制非常重要。要获取Cookie：

  1. 使用浏览器登录百度百科

  2. 使用浏览器开发者工具(F12)，在网络请求中查看任意百科API请求的Cookie头

  3. 复制完整的Cookie值，放入.env文件的BAIKE_COOKIE字段中

  4. Cookie示例格式：PSTM=1709884903; BIDUPSID=AC7D9378915FB2E7A091826DB946A7BA; ...

注意：Cookie包含敏感信息，请勿将其提交到版本控制系统或分享给他人。

使用方法

启动服务器

npm start

开发模式

npm run dev

功能

request_baike 工具

该工具允许获取特定百度百科词条的讨论数据。

参数：

render_baike 提示模板

该提示模板基于获取的百科讨论数据，生成一份全面的分析，包括：

  1. 讨论的主要话题

  2. 主要观点及其倾向

  3. 热门讨论

  4. 反映的社会热点或技术趋势

  5. 词条主题的重要性和影响力

示例

// 获取百科讨论数据
const result = await mcp.tools.request_baike({ url: "https://baike.baidu.com/item/DeepSeek" });

// 生成百科内容分析
const prompt = await mcp.prompts.render_baike({ url: "https://baike.baidu.com/item/DeepSeek" });

Available Tools

1 tool
request_baikeD
ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes百度百科URL，例如：https://baike.baidu.com/item/DeepSeek

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'request_baike' stands alone with no competing alternatives for an agent to confuse it with.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The tool name 'request_baike' follows a clear verb_noun pattern, but consistency cannot be assessed across a set of one.

Tool Count2/5

A single tool is too few for most server purposes, as it severely limits functionality and suggests the server may be incomplete or trivial. Without a description, it's unclear if this minimal surface is justified, but typically one tool indicates under-scoping.

Completeness1/5

With only one tool and no description, it's impossible to assess coverage of any domain. The server appears severely incomplete, as a single 'request_baike' tool likely cannot handle a full workflow or lifecycle for Baike-related tasks, leaving obvious gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • mediawiki-mcp-server

    shiquda
    F
    license
    B
    quality
    C
    maintenance
    A MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!
    2
    26

  • Wikipedia MCP Server

    danbunnell
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that retrieves and provides Wikipedia content for requested topics, enabling easy access to Wikipedia information directly through the Model Control Protocol.
    1

  • Douyin Video Analysis MCP

    youzhajun
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that parses Douyin share links and performs intelligent content analysis using the Doubao video understanding model. It provides structured outputs including video summaries, categorized outlines, and step-by-step tutorial information.
    1
    2
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zzzccs123/mcp-baike-render'

If you have feedback or need assistance with the MCP directory API, please join our Discord server