Google Scholar

Created By
JackKuo666a year ago
Overview

What is Google Scholar MCP Server?

The Google Scholar MCP Server enables AI assistants to search and access Google Scholar papers through a simple Model Context Protocol (MCP) interface, allowing programmatic access to academic papers.

How to use Google Scholar MCP Server?

To use the server, install it via Smithery or manually clone the repository, install dependencies, and run the server. You can then use the provided MCP tools in your AI assistant or application.

Key features of Google Scholar MCP Server?

  • Paper Search: Query Google Scholar papers with custom search strings or advanced search parameters.
  • Efficient Retrieval: Fast access to paper metadata.
  • Author Information: Retrieve detailed information about authors.
  • Research Support: Facilitate academic research and analysis.

Use cases of Google Scholar MCP Server?

  1. Searching for academic papers on specific topics.
  2. Performing advanced searches by author or publication year.
  3. Retrieving detailed author information for research purposes.

FAQ from Google Scholar MCP Server?

  • Can I use this server for all academic fields?

Yes! The server can be used to search for papers across various academic disciplines available on Google Scholar.

  • Is there a cost to use the Google Scholar MCP Server?

No! The server is free to use for everyone.

  • What are the system requirements?

The server requires Python 3.10+ and specific dependencies listed in the project.

Server Config

{
  "mcpServers": {
    "Google-Scholar": {
      "command": "bash",
      "args": [
        "-c",
        "source /home/YOUR/PATH/.venv/bin/activate && python /home/YOUR/PATH/Google-Scholar-mcp-server.py"
      ],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago