Google Scholar
$0.01/call
Search Google Scholar for academic papers and citations
Connect Google Scholar tools
Cursor
Claude Code
Claude Desktop
Windsurf
VS Code
Cline
Roo Code
ChatGPT
Gemini CLI
Amazon Q
Goose
Augment
n8n
API / cURL
AI SDK
TypeScript SDK
{
"mcpServers": {
"google-scholar": {
"url": "https://google-scholar.mcp.xpay.sh/mcp?key=YOUR_API_KEY"
}
}
}Or connect all tools
Access all tools (including Google Scholar) through a single MCP connection.
{
"mcpServers": {
"xpay": {
"url": "https://mcp.xpay.sh/mcp?key=YOUR_API_KEY"
}
}
}Agent Discovery
Machine-readable catalogs for LLM agents and automation.
curl https://xpay.tools/llms.txt
curl https://xpay.tools/agents.txt
curl https://xpay.tools/skill.md
Pricing
Pay per tool call. No subscriptions.
1 Google Scholar tool availableAbout Google Scholar
Google Scholar on xpay — Academic research at per-call pricing
Google Scholar is the go-to search engine for academic papers, citations, and research articles. Developers integrate it to build literature review tools, citation aggregators, research dashboards, and AI-powered paper discovery systems. Traditionally, this meant either scraping (fragile, slow) or negotiating custom access. xpay wraps Google Scholar as an MCP tool, letting you call it directly from Claude Code, Cursor, or any MCP-compatible agent—paying only for what you use, with no per-provider signup.
What's available
search_google_scholar($0.01/call) — Search Google Scholar for academic papers and research articles. Supports filtering by author, publication year range, and returns structured results with titles, authors, abstracts, and URLs.
When Google Scholar is the right tool
- Building a literature review or research paper discovery system
- Aggregating citations and author publication histories
- Enriching academic datasets with paper metadata and abstracts
- Automating research workflows that need to find papers by topic, author, or date range
- Creating AI-powered research assistants that need to cite peer-reviewed sources
- Analyzing publication trends across institutions or research fields
When to choose something else
- If you need full-text PDF access or content extraction, Google Scholar returns metadata only; you'd need to fetch PDFs separately from publisher sites or preprint servers
- If you're doing large-scale bulk research (thousands of queries), consider negotiating direct API access with Google or using academic databases like PubMed or arXiv for specialized domains
- If you need real-time alerts or subscription-based features (saved searches, email notifications), Google Scholar's web interface or institutional subscriptions may be more suitable
- If your use case is purely internal and doesn't require live web data, a static academic dataset or local corpus may be cheaper and faster
Pricing snapshot
| Tool | Price per call |
|---|---|
search_google_scholar | $0.01 |
Quickstart
Add the Google Scholar MCP endpoint to Claude Code:
claude mcp add --transport http google-scholar "https://google-scholar.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"
Once connected, ask your Claude Code agent to use search_google_scholar with a query, author filter, or year range—the tool will return structured paper metadata and you'll be billed $0.01 per search.
Alternatively, connect all xpay providers in one MCP endpoint:
claude mcp add --transport http xpay "https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"
With the unified endpoint, use xpay_discover("google scholar") to find the tool, then xpay_run("google-scholar/search_google_scholar", {...args}) to execute it.
Why route Google Scholar through xpay?
- No Google Scholar account needed — xpay holds the credentials; you authenticate once with your xpay API key
- Pay only per call — $0.01 per search, no subscription or monthly fees; stop paying when you stop searching
- MCP-native integration — Call Google Scholar directly from Claude Code, Cursor, Windsurf, Cline, or any MCP client without custom HTTP wrappers
- Unified billing — Combine Google Scholar with other xpay providers (Tavily, Apollo, etc.) under one API key and invoice
- Instant provisioning — Sign up with email or Google, get your key, and start searching in seconds
Frequently Asked Questions
Google Scholar on xpay is an MCP-wrapped interface to Google Scholar's academic paper search. Instead of building your own scraper or negotiating direct API access, you connect an MCP endpoint to Claude Code or Cursor and call `search_google_scholar` directly. xpay handles authentication and billing; you pay $0.01 per search.
No. xpay holds Google Scholar credentials on your behalf. You only need an xpay account (sign up at https://xpay.tools with email or Google), get your API key, and you're ready to search. No per-provider signup required.
Each call to `search_google_scholar` costs $0.01. There are no subscriptions, monthly minimums, or per-provider fees. You're billed only for searches you run. New xpay accounts include $5 free credit.
Run `claude mcp add --transport http google-scholar "https://google-scholar.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"` in your terminal, replacing YOUR_XPAY_KEY with your key from https://xpay.tools. Claude Code will then have access to the `search_google_scholar` tool.
Add an entry to your `mcp.json` configuration file (usually in `.cursor/mcp.json` or `.vscode/mcp.json`): `{ "mcpServers": { "google-scholar": { "url": "https://google-scholar.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY" } } }`. Restart your editor and the tool will be available.
`search_google_scholar` lets you search by keyword, filter by author name, and specify publication year ranges. It returns structured results with paper titles, authors, abstracts, and URLs. You can use it to find papers on any academic topic, discover an author's publication history, or build a research dataset.
You could scrape Google Scholar directly (fragile, slow, violates ToS), negotiate custom API access with Google (expensive, slow approval), use academic-specific APIs like PubMed or arXiv (limited to those domains), or subscribe to institutional databases. xpay offers a middle ground: instant, per-call, no signup.
Yes. Use the unified xpay endpoint (`https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY`) to connect all providers—Google Scholar, Tavily, Apollo, and others—in a single MCP connection. All calls are billed under one xpay account.