Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Google Scholar search results, citation counts and citation export formats, as structured JSON.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
HASDATA_API_KEY, x-api-key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"google-scholar": {
"command": "npx",
"args": [
"-y",
"@hasdata/google-scholar-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http google-scholar 'https://mcp.hasdata.com/mcp?apis=google_scholar' --header 'x-api-key: your-value'claude mcp add google-scholar --env HASDATA_API_KEY=your-value -- npx -y @hasdata/google-scholar-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"google-scholar": {
"url": "https://mcp.hasdata.com/mcp?apis=google_scholar",
"headers": {
"x-api-key": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"google-scholar": {
"command": "npx",
"args": [
"-y",
"@hasdata/google-scholar-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"google-scholar": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=google_scholar",
"headers": {
"x-api-key": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"google-scholar": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hasdata/google-scholar-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
x-api-key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 hasdata.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:HASDATA_API_KEY, x-api-key
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.0.2)于43天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A hosted Google Scholar MCP server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Google Scholar tools. Search the literature with Scholar's own operators, year ranges and cited-by lookups, then pull a paper's citation in five styles with its BibTeX and EndNote export links, both as structured JSON, with nothing to host.
It reads public Google Scholar pages that a signed-out visitor can see.
1,000 free credits every month, no card required, which is 100 Scholar calls at the 10-credit rate.
https://mcp.hasdata.com/mcp?apis=google_scholar
An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/google-scholar-mcp on npm and hasdata-google-scholar-mcp on PyPI, shown below.
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
| Field | Value |
|---|---|
| URL | https://mcp.hasdata.com/mcp?apis=google_scholar |
| Transport | HTTP, streamable |
| Auth header | x-api-key: HASDATA_API_KEY |
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
Claude Code
claude mcp add --transport http google-scholar "https://mcp.hasdata.com/mcp?apis=google_scholar" \
--header "x-api-key: HASDATA_API_KEY"
Claude Desktop
Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=google_scholar and sign in.
For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/google-scholar-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:
{
"mcpServers": { "google-scholar": { "command": "npx", "args": ["-y", "@hasdata/google-scholar-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:
{
"mcpServers": { "google-scholar": { "command": "uvx", "args": ["hasdata-google-scholar-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
Cursor
~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": { "google-scholar": { "url": "https://mcp.hasdata.com/mcp?apis=google_scholar", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Windsurf
~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:
{
"mcpServers": { "google-scholar": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=google_scholar", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
VS Code
.vscode/mcp.json in the workspace:
{
"servers": { "google-scholar": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=google_scholar", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Each of these lands on one tool, or on two in sequence when the second needs an id the first returns.
A prompt naming a paper takes two calls, one search to reach its resultId and one citation lookup. A prompt about who cites a paper also takes two, because the second call reuses citedBy.citesId from the first.
| Tool | What it returns |
|---|---|
hasdata_google_scholar_case_law_getScholarCaseLawOpinion | One court opinion with its court, reporter citation, docket numbers, argued and decided dates, and every case it cites with its own caseId. 10 credits a call |
hasdata_google_scholar_cite_getScholarCitationFormats | Formatted citation snippets (MLA, APA, Chicago, Harvard, Vancouver) and reference-manager export links (BibTeX, EndNote, RefMan, RefWorks). 10 credits a call |
hasdata_google_scholar_scholar_getScholarSearchResults | Each organic result with title, link, snippet, publication info (authors with profile links), cited-by count and link, related-articles link, and all-versions count and…. 10 credits a call |
Three tools, 10 credits per successful call.
hasdata_google_scholar_scholar_getScholarSearchResults
A page of Scholar results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
q | string | yes | The query. Scholar operators such as author: and source: work here |
asYlo / asYhi | number | Published from and up to these years | |
start | number | Result offset, where 0 is the first result | |
num | number | Results per page | |
scisbd | number | 1 sorts abstracts by date, 2 sorts everything by date. Omit for relevance | |
cites | string | Find articles citing this one, using a citedBy.citesId | |
cluster | string | Find every indexed version of an article, using a versions.clusterId | |
asSdt | string | Search type, 0,5 for articles, 4 for case law, 0 or 7 for patents | |
asRr | number | 1 returns review articles only | |
asVis | number | 1 excludes citations, 0 includes them | |
hl | string | Interface language, one of 159 | |
lr | array | Restrict to these content languages | |
safe | string | active or off | |
filter | number | 1 keeps Google's similar and omitted result filters, 0 drops them |
Returns searchInformation with totalResults, queryDisplayed and the time Scholar reported, an organicResults array, and pagination.
Each result carries position, resultId, title, link, snippet, a publicationInfo object, a resources array, citedBy, versions, relatedPagesLink and citeHasdataLink.
publicationInfo.authors is the part worth knowing about. Alongside the raw summary line it lists the authors Scholar has profiles for, each with a name, a profile link and an authorId, which is how you follow one author rather than parsing a byline.
citedBy and versions are the two ids that make this tool compose with itself. citedBy.citesId goes back into cites to walk a citation graph, and versions.clusterId goes into cluster to see every indexed copy of the same paper.
{
"position": 1, "resultId": "A7L9JolPKkoJ", "title": "A historical survey of advances in transformer architectures", "link": "https://www.mdpi.com/2076-3417/14/10/4316", "snippet": "… of the Vision Transformer (ViT) opening a new realm of architectures which build … transformer architecture, it becomes pertinent to examine in detail the architecture of the transformer …", "publicationInfo": { "summary": "AR Sajun, I Zualkernan, D Sankalpa - Applied Sciences, 2024 - mdpi.com", "authors": [ { "name": "AR Sajun", "authorId": "k6zWX4EAAAAJ", "link": "https://scholar.google.com/citations?user=k6zWX4EAAAAJ&hl=en" } ] }, "resources": [{ "fileFormat": "Html", "title": "mdpi.com", "link": "https://www.mdpi.com/2076-3417/14/10/4316" }], "citedBy": { "total": 97, "citesId": "5344171358311789059" }, "versions": { "total": 7, "clusterId": "5344171358311789059" } }
hasdata_google_scholar_cite_getScholarCitationFormats
The citation block for one paper.
| Parameter | Type | Required | Notes |
|---|---|---|---|
q | string | yes | A resultId from a search result, not a search query |
hl | string | Interface language |
Returns citations, the formatted string in MLA, APA, Chicago, Harvard and Vancouver, and links, the export URLs for BibTeX, EndNote, RefMan and RefWorks.
{
"citations": [ { "title": "APA", "snippet": "Sajun, A. R., Zualkernan, I., & Sankalpa, D. (2024). A historical survey of advances in transformer architectures. Applied Sciences, 14(10), 4316." } ], "links": [ { "name": "BibTeX", "link": "https://scholar.googleusercontent.com/scholar.bib?q=info:A7L9JolPKkoJ:scholar.google.com/&output=citation..." } ] }
hasdata_google_scholar_case_law_getScholarCaseLawOpinion
One court opinion, with the cases it cites.
| Parameter | Type | Required | Notes |
|---|---|---|---|
caseId | string | yes | A caseId from a case-law search result, not a search query |
hl | string | Interface language |
The id comes from the search tool rather than from a URL. Set asSdt to a case-law court scope, for example 4, and every organic result then carries caseId beside caseHasdataLink.
Returns caseResults with title, name, courtName, cert, and the firstPage and lastPage of the printed opinion. dates holds the argued and decided dates as separate entries, `s
只显示了开头部分;其余内容请在仓库中阅读