ScholarFetch
Server Details
Multi-engine scholarly research server for search, traversal, full text, and reading lists.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- laibniz/scholarfetch
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 12 of 12 tools scored.
Each tool has a distinct purpose with clear boundaries: abstract retrieval, full-text reading, author disambiguation, paper listing, DOI enrichment, reference expansion, and saved list management (add, clear, export, list, remove). The descriptions explicitly differentiate overlapping functions like abstract vs. article_text, and author_candidates vs. author_papers, preventing confusion.
All tools follow a consistent 'scholarfetch_' prefix with snake_case naming and clear verb_noun patterns (e.g., scholarfetch_abstract, scholarfetch_author_candidates, scholarfetch_saved_add). The naming is predictable and uniform across the entire set, making it easy for an agent to understand each tool's role.
With 12 tools, the server is well-scoped for academic research tasks, covering key workflows like paper discovery, author exploration, metadata enrichment, and reading list management. Each tool serves a specific function without redundancy, and the count aligns with the domain's complexity, avoiding both thinness and bloat.
The tool set provides comprehensive coverage for academic research: it supports discovery (search, author_papers), metadata access (abstract, doi_lookup), content retrieval (article_text), graph traversal (references), and session management (saved_* tools). There are no obvious gaps; the surface enables end-to-end research workflows without dead ends.
Available Tools
12 toolsscholarfetch_abstractInspect
Read the best abstract available for a paper. Use with a DOI or with author_name + candidate_index + paper_index after author_papers. If you pass engines, use a comma-separated subset of: elsevier, openalex, crossref, arxiv, europepmc, springer, semanticscholar.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | No | ||
| engines | No | ||
| author_name | No | ||
| paper_index | No | ||
| candidate_index | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_article_textInspect
Read full paper text when machine-readable content is recoverable. Use with a DOI or with author_name + candidate_index + paper_index. Uses Elsevier first, then open-access fallbacks such as Springer OA, Europe PMC, arXiv PDF, and generic PDF URLs when text is recoverable. If you pass engines, use a comma-separated subset of: elsevier, openalex, crossref, arxiv, europepmc, springer, semanticscholar.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | No | ||
| engines | No | ||
| author_name | No | ||
| paper_index | No | ||
| candidate_index | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_author_candidatesInspect
Disambiguate a human author name into ranked identity candidates. Use this before scholarfetch_author_papers when the name is ambiguous and you need a stable candidate_index. If you pass engines, it must include openalex.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| limit | No | ||
| engines | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_author_papersInspect
Expand one author into a deduplicated paper list. This is the main author->paper traversal tool and supports research filters. Use author_id when you already know the exact author, or author_name plus candidate_index after scholarfetch_author_candidates. Supported comma-separated filters: year>=YYYY, year<=YYYY, year=YYYY, has:abstract, has:doi, has:pdf, venue:, title:, doi:. If you pass engines, it must include openalex.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| engines | No | ||
| filters | No | ||
| author_id | No | ||
| author_name | No | ||
| candidate_index | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_doi_lookupInspect
Enrich one known DOI with metadata, reading links, and full-text availability signals. If you pass engines, use a comma-separated subset of: elsevier, openalex, crossref, arxiv, europepmc, springer, semanticscholar.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | Yes | ||
| engines | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_referencesInspect
Expand a paper into its references. Use with a DOI or with author_name + candidate_index + paper_index. This is the main edge-expansion tool for traversing the literature graph. If you pass engines, use a comma-separated subset of: elsevier, openalex, crossref, arxiv, europepmc, springer, semanticscholar.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | No | ||
| engines | No | ||
| author_name | No | ||
| paper_index | No | ||
| candidate_index | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_saved_addInspect
Add one paper to a named in-memory reading list on the MCP server. Best input is paper_json copied from another ScholarFetch tool result, but DOI, query+result_index, or author_name+candidate_index+paper_index also work. Reuse the same collection name across calls to keep one research session together.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | No | ||
| query | No | ||
| engines | No | ||
| collection | No | default | |
| paper_json | No | ||
| author_name | No | ||
| paper_index | No | ||
| result_index | No | ||
| candidate_index | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_saved_clearInspect
Clear all papers from a named in-memory reading list. Useful when restarting a research branch.
| Name | Required | Description | Default |
|---|---|---|---|
| collection | No | default |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_saved_exportInspect
Export the current reading list as citations, abstracts, BibTeX, or an aggregated full-text corpus. Valid format values: citations, abstracts, bib, fulltext. Valid style values when format=citations: harvard, apa, ieee. Use include_references=true with format=fulltext when you want a richer downstream synthesis corpus.
| Name | Required | Description | Default |
|---|---|---|---|
| style | No | harvard | |
| format | No | citations | |
| engines | No | ||
| collection | No | default | |
| include_references | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_saved_listInspect
List all papers currently saved in a named in-memory reading list. Use this to inspect the working set before exporting or removing items.
| Name | Required | Description | Default |
|---|---|---|---|
| collection | No | default |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_saved_removeInspect
Remove one paper from a named in-memory reading list by DOI or exact title.
| Name | Required | Description | Default |
|---|---|---|---|
| doi | No | ||
| title | No | ||
| collection | No | default |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
scholarfetch_searchInspect
Start a research traversal from keywords, a DOI, or a person name. Returns deduplicated paper records that you can inspect, save, expand through references, or use as seeds for author exploration. If you pass engines, use a comma-separated subset of: elsevier, openalex, crossref, arxiv, europepmc, springer, semanticscholar.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | ||
| engines | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!