SemanticScholar_MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEMANTIC_SCHOLAR_API_KEY | No | Optional Semantic Scholar API key. The MCP servers automatically use the key when it is present and otherwise remain unauthenticated where Semantic Scholar permits anonymous access. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| 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 |
|---|---|
| get_paperB | Get one paper by Semantic Scholar ID or supported external identifier. |
| get_papersA | Batch-get up to 500 caller-supplied paper identifiers. |
| search_papersC | Run one token-paginated This endpoint returns up to 1000 papers per upstream call and does not
accept a |
| search_papers_relevanceB | Run one relevance-ranked Relevance search is limited by Semantic Scholar to 100 results per call and 1000 relevance-ranked results total. |
| get_citationsC | Get one page of papers that cite the requested paper. |
| get_referencesC | Get one page of references cited by the requested paper. |
| get_authorC | Get one Semantic Scholar author by author ID. |
| get_authorsB | Batch-get up to 1000 Semantic Scholar author IDs. |
| search_authorsC | Search authors by name using one offset-paginated request. |
| get_author_papersC | Get one page of papers associated with a Semantic Scholar author. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools are mostly distinct: get_authors/get_author differ by batch vs single ID, and search_papers vs search_papers_relevance are differentiated by bulk vs relevance-ranked semantics. The only slight confusion is the two search variants, but descriptions clarify their differing endpoints.
Naming follows a consistent verb_noun pattern with get_ for retrieval and search_ for querying. search_papers_relevance is a minor deviation from the simple object naming, but it remains readable and predictable.
10 tools is well-scoped for a scholarly search and retrieval API, covering authors, papers, citations, references, and author-paper relationships without unnecessary redundancy.
The surface covers the core academic search workflows: author lookup, single/batch paper retrieval, external ID support, bulk and relevance search, citations, references, and author-associated papers. For a read-only domain, no major gaps are apparent.