scholar-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | 标准代理环境变量(备选) | |
| HTTPS_PROXY | No | 标准代理环境变量(备选) | |
| SCHOLAR_PROXY | No | 代理地址,优先级最高 | http://localhost:7890 |
| SCHOLAR_RETRIES | No | 搜索失败最大重试次数 | 3 |
| SCHOLAR_TIMEOUT | No | 单次 HTTP 请求超时(秒) | 30 |
| SCHOLAR_NO_PROXY | No | 设为 1/true/yes 禁用代理 | |
| SCHOLAR_CHART_PORT | No | 图表 HTTP 服务端端口 | 8765 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_papersA | 搜索学术论文,支持双搜索引擎. 单次请求最多返回 30 条结果,已内置请求间隔和限流重试。 Args: query: 搜索关键词,英文效果最佳,如 "graph neural network recommendation" num_results: 返回论文数量,1-30,默认 10 year_low: 发表年份下限,如 2020 year_high: 发表年份上限,如 2024 engine: 搜索引擎 — "bing"(默认, 免代理), "google"(需代理), "auto"(Bing优先, 失败自动切Google) |
| get_paper_detailA | 获取单篇论文的详细信息,自动从外部源获取完整摘要. Args: title: 论文标题(精确匹配效果更好) url: 论文 URL(Google Scholar URL 仅限 engine=google 时使用,与 title 二选一) engine: 搜索引擎 — "bing"(默认, 免代理), "google"(需代理), "auto"(Bing优先, 失败切Google) |
| analyze_relevanceA | 分析一组论文与研究主题的相关性,返回排序结果和分析摘要. 典型用法:先调用 search_papers 获取论文列表,再将返回的 JSON 传入此方法。 Args: topic: 研究主题描述(英文 1-3 句话),如 "using graph neural networks for collaborative filtering recommendation systems" papers_json: search_papers 返回的 JSON 字符串,需包含 papers 数组 |
| generate_relevance_chartA | 生成多角度论文相关性分析图表,启动本地 HTTP 服务端返回链接. 生成 3 张图表:相关性柱状图、K-Means 聚类散点图、TF-IDF 关键词分析。 图表通过本地 HTTP 服务端 (http://localhost:8765) 提供,在浏览器中打开。 返回 message 字段含 markdown 链接和原始 URL,客户端可渲染或复制。 典型用法:先调用 analyze_relevance 获取排序结果,再将其 JSON 传入此方法。 Args: topic: 研究主题描述(图表标题) papers_json: analyze_relevance 返回的 JSON 字符串,需包含 ranked_papers 数组 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/MuliMuri/scholar_search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server