# How to connect Semantic Scholar to OpenClaw (paste one key, 20 tools)

> Connect Semantic Scholar to OpenClaw with ClawLink: paste your Semantic Scholar key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/semanticscholar

The usual route to Semantic Scholar access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Semantic Scholar setup: install one ClawHub skill, connect Semantic Scholar in the browser, and OpenClaw can call real Semantic Scholar actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect OpenClaw to Semantic Scholar.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Semantic Scholar** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Paste this into OpenClaw to set up ClawLink:**

> I want to connect my apps to OpenClaw through ClawLink.
> Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin`
> When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect semanticscholar  # connect Semantic Scholar (browser OAuth)
npx -y @useclawlink/cli actions semanticscholar  # list available actions
npx -y @useclawlink/cli run semanticscholar <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

```bash
openclaw plugins install clawhub:clawlink-plugin
```

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Semantic Scholar in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Semantic Scholar API key once.

Verify the connection by asking OpenClaw:

> Use Semantic Scholar to details about a paper and walk me through the result in plain English.

### Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Semantic Scholar is connected in the dashboard, that agent calls the same 20 Semantic Scholar tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Semantic Scholar MCP for OpenClaw

Looking for a Semantic Scholar MCP server for OpenClaw? ClawLink connects Semantic Scholar to OpenClaw and exposes 20 Semantic Scholar tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Semantic Scholar integration](https://claw-link.dev/hermes/semanticscholar) works the same way.

## What the OpenClaw Semantic Scholar integration can do

20 Semantic Scholar tools are ready for OpenClaw once the account is connected.

### All 20 Semantic Scholar tools for OpenClaw

| Tool | What it does |
|---|---|
| **Details about a paper** `semanticscholar_details_about_a_paper` | Examples: \<ul> |
| **Details about a paper s authors** `semanticscholar_details_about_a_paper_s_authors` | Retrieves the list of authors for a specific paper identified by its unique paper_id in the |
| **Details about a paper s citations** `semanticscholar_details_about_a_paper_s_citations` | Retrieves a list of citations for a specific academic paper using its unique Semantic Scholar |
| **Details about a paper s references** `semanticscholar_details_about_a_paper_s_references` | Retrieves the list of references cited by a specific paper in the Semantic Scholar database |
| **Details about an author** `semanticscholar_details_about_an_author` | Retrieve detailed information about an author from Semantic Scholar, including name |
| **Details about an author s papers** `semanticscholar_details_about_an_author_s_papers` | Retrieves a list of papers authored or co-authored by a specific researcher identified by their |
| **Get dataset** `semanticscholar_get_dataset` | Get download links for a specific dataset within a release |
| **Get dataset diffs** `semanticscholar_get_dataset_diffs` | Get download links for incremental diffs between dataset releases |
| **Get details for multiple authors at once** `semanticscholar_get_details_for_multiple_authors_at_once` | Retrieves detailed information for multiple authors from Semantic Scholar in a single API call |
| **Get details for multiple papers at once** `semanticscholar_get_details_for_multiple_papers_at_once` | Retrieve detailed information for multiple academic papers in a single API call using the |
| **Get paper recommendations** `semanticscholar_get_paper_recommendations` | Get paper recommendations based on positive and negative example papers |
| **Get recommendations for paper** `semanticscholar_get_recommendations_for_paper` | Get recommended papers for a single positive example paper |
| **Get release** `semanticscholar_get_release` | Retrieve metadata for a specific Semantic Scholar dataset release |
| **List releases** `semanticscholar_list_releases` | List all available dataset releases from Semantic Scholar |
| **Paper title search** `semanticscholar_paper_title_search` | Behaves similarly to \<code>/paper/search\</code>, but is intended for retrieval of a single |
| **Search bulk papers** `semanticscholar_search_bulk_papers` | Perform bulk search for academic papers |
| **Search for authors by name** `semanticscholar_search_for_authors_by_name` | Search for academic authors in the Semantic Scholar database by name |
| **Search papers** `semanticscholar_search_papers` | Search for academic papers by relevance in the Semantic Scholar database |
| **Suggest paper query completions** `semanticscholar_suggest_paper_query_completions` | Get autocomplete suggestions for paper queries |
| **Text snippet search** `semanticscholar_text_snippet_search` | Search for text snippets (~500 words) within academic papers that match your natural language |

## Example prompts

**Details About A Paper**

> Use Semantic Scholar to details about a paper and walk me through the result in plain English.

**Details About A Paper S Authors**

> Use Semantic Scholar to details about a paper s authors and walk me through the result in plain English.

**Details About A Paper S Citations**

> Use Semantic Scholar to details about a paper s citations and walk me through the result in plain English.

**Details About A Paper S References**

> Use Semantic Scholar to details about a paper s references and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Semantic Scholar working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Semantic Scholar API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Semantic Scholar account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Semantic Scholar. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Semantic Scholar actions to the runtime in a format your agent can reliably use. | 20 tools for Semantic Scholar are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Semantic Scholar to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Semantic Scholar in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Semantic Scholar key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Semantic Scholar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Semantic Scholar, but the calls run through the ClawLink plugin and your connected account. Make sure Semantic Scholar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

### Connection succeeds but no tools appear
Reconnect Semantic Scholar from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Semantic Scholar tools
Semantic Scholar tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Semantic Scholar call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Semantic Scholar returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Semantic Scholar has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Semantic Scholar integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Semantic Scholar: link your Semantic Scholar account once in the browser and OpenClaw can call the Semantic Scholar API through 20 ready-made tools — no custom code or token handling.

### How do I add Semantic Scholar to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Semantic Scholar skill from ClawHub, then you click Connect in the dashboard to authorize Semantic Scholar. OpenClaw calls the tools from the next message — no config files, and the Semantic Scholar key you paste is stored server-side instead of in your environment.

### How long does it take to connect Semantic Scholar to OpenClaw?
About two minutes. Sign in, click Connect next to Semantic Scholar in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Semantic Scholar up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Semantic Scholar working from chat.

### OpenClaw installed the Semantic Scholar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Semantic Scholar, but the calls run through the ClawLink plugin and your connected account. Make sure Semantic Scholar is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

## Related

- [OpenClaw DataRobot integration](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
- [OpenClaw Chatbotkit integration](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
- [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.