Semantic Scholar MCP integration for AI agents.
Connect AI agents to Semantic Scholar through 16 structured actions, including bulk search papers, autocomplete papers, and get author. Review authentication…
- ACTION CONTRACTS
- 16
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Semantic Scholar integration exposes
The Semantic Scholar Agent App exposes 16 provider-backed actions for ai and data work. Its current contract lets an authorized agent bulk-search semantic scholar papers and page through large result sets with tokens, suggest semantic scholar paper query completions, and get details for a semantic scholar author. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Semantic Scholar account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Semantic Scholar capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
bulk_search_papersREADBulk-search Semantic Scholar papers and page through large result sets with tokens.
INPUTS: query / fields / limit / token / year
autocomplete_papersREVIEWSuggest Semantic Scholar paper query completions.
INPUTS: query / limit
get_authorREADGet details for a Semantic Scholar author.
INPUTS: authorId / fields
get_author_papersREADList papers written by a Semantic Scholar author.
INPUTS: authorId / fields / limit / offset
get_authorsREADGet details for multiple Semantic Scholar authors at once.
INPUTS: authorIds / fields
get_paperREADGet details for a Semantic Scholar paper by paper ID or external identifier.
INPUTS: paperId / fields
get_paper_authorsREADList authors for a Semantic Scholar paper.
INPUTS: paperId / fields / limit / offset
get_paper_citationsREADList papers that cite a Semantic Scholar paper.
INPUTS: paperId / fields / limit / offset
get_paper_referencesREADList papers referenced by a Semantic Scholar paper.
INPUTS: paperId / fields / limit / offset
get_papersREADGet details for multiple Semantic Scholar papers at once.
INPUTS: paperIds / fields
match_paper_titleREVIEWFind the best Semantic Scholar paper match for a paper title.
INPUTS: query / fields
recommend_for_paperREVIEWGet recommended Semantic Scholar papers for one positive example paper.
INPUTS: paperId / fields / limit
INPUT CONTRACTS
Know what the action needs before it runs.
bulk_search_papers
queryREQUIRED- The plain-text search query. Semantic Scholar does not support special query syntax.
fieldsOPTIONAL- A comma-separated list of Semantic Scholar fields to return, using dot notation for nested fields when needed.
limitOPTIONAL- The maximum number of results to return.
tokenOPTIONAL- The continuation token returned by Semantic Scholar.
yearOPTIONAL- The publication year or inclusive year range, such as 2019, 2016-2020, 2010-, or -2015.
autocomplete_papers
queryREQUIRED- The plain-text search query. Semantic Scholar does not support special query syntax.
limitOPTIONAL- The maximum number of results to return.
get_author
authorIdREQUIRED- The Semantic Scholar author ID.
fieldsOPTIONAL- A comma-separated list of Semantic Scholar fields to return, using dot notation for nested fields when needed.
get_author_papers
authorIdREQUIRED- The Semantic Scholar author ID.
fieldsOPTIONAL- A comma-separated list of Semantic Scholar fields to return, using dot notation for nested fields when needed.
limitOPTIONAL- The maximum number of results to return.
offsetOPTIONAL- The zero-based pagination offset.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Bulk Search Papers
Bulk-search Semantic Scholar papers and page through large result sets with tokens. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
bulk_search_papersVerify with Get Author
Get details for a Semantic Scholar author. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_authorSAFETY BOUNDARY
Operate Semantic Scholar with explicit limits
- Authorize Semantic Scholar with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Semantic Scholar data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Semantic Scholar rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Semantic Scholar task completed successfully.
CONNECTION MODEL
API key
Semantic Scholar API key sent in the x-api-key header. Request a key from the official API page: https://www.semanticscholar.org/product/api#api-key-form.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Semantic Scholar.