openalex_mcp_search_works – 1 MCP server offers this tool
What it usually takes
author– in 1 of 1corpus– in 1 of 1date_from– in 1 of 1date_to– in 1 of 1domain– in 1 of 1exact– in 1 of 1field– in 1 of 1filter_open_access– in 1 of 1institution– in 1 of 1institution_scope– in 1 of 1max_results– in 1 of 1query– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
OpenAlex MCP Demo co.huggingface.geraldine/openalex-mcp Search OpenAlex for academic works by keyword query. Query syntax: "phrase in quotes", "near each other"~5, fuzzy~2, AND/OR/NOT in uppercase. Wildcards (* and ?) work only with exact=true. Calls run on the anonymous daily budget unless an X-Openalex-Api-Key request header is sent, or the deployment configured a key of its own. Returns: {"source": "openalex", "command": "search_works", "total_found": int, "returned": int, "query_used": str, "filters_used": [str], "corpus": str, "oql": str | null, "cost_usd": float | null, "results": [{"source": "openalex", "id": str, "title": str, "authors": [str], "doi": str | null, "url": str, "year": int | null, "journal": str | null, "fwci": float | null, "primary_topic": object | null, "topics": [object]}], "error": str | null} | author,corpus,date_from,date_to,domain,exact,field,filter_open_access,institution,institution_scope,max_results,query,sort_by,subfield,topic,topic_scope | Not stated |