Web of Science MCP bridge
Search Web of Science Core Collection from an MCP client using your Clarivate Starter API key. Find papers, retrieve bibliographic records, and pass a DOI to Europe PMC and OpenAlex to look for an abstract, open-access links or available full-text sections.
The bridge supports topics across disciplines, from quantum computing to urban climate and veterinary medicine. WoS coverage depends on your subscription. Europe PMC focuses on life sciences and biomedical literature. Clarivate Starter supplies bibliographic metadata. Abstracts and open-access text come from the literature tools when available.
Try it without credentials
Install Python 3.12 and uv 0.13.9. From a checkout or unpacked source distribution, install the locked runtime environment and run the example:
uv sync --locked --no-dev --python 3.12
uv run --locked --no-dev python scripts/demo.py
The script calls the installed server over MCP stdio. An in-process HTTP fixture inside that server subprocess supplies the synthetic record. The call is:
{"name": "search", "arguments": {"query": "TS=(quantum computing)"}}
The synthetic result printed by the demo is:
{
"results": [
{
"id": "WOS:SMOKE001",
"title": "Synthetic quantum computing paper",
"url": "https://www.webofscience.com/wos/woscc/full-record/WOS:SMOKE001"
}
]
}
Run with your WoS key
Install the package from PyPI with uv tool install wos-mcp-bridge.
Configure your MCP client to launch the installed wos-mcp-bridge command over
stdio. Use the client's secret settings to pass WOS_API_KEY to the process.
OPENALEX_API_KEY is optional. The application reads environment variables at
startup. For a local check from Bash:
read -rsp 'Clarivate Starter API key: ' WOS_API_KEY
echo
export WOS_API_KEY
wos-mcp-bridge
The process waits for an MCP client on stdin and stdout. You can verify the
installation without credentials using wos-mcp-bridge --version.
Set WOS_MCP_PROFILE=literature to use the four Europe PMC and OpenAlex tools
without a Clarivate key. See the deployment guide for
authenticated Streamable HTTP and managed hosting.
Tools
| Tool | Purpose |
|---|---|
search(query) |
First 10 results by relevance; returns id, title, and url. |
fetch(id) |
Bibliographic metadata for a WOS: accession ID; not an article PDF. |
search_wos(query, limit=10, page=1, sort="RS+D") |
One page of detailed results, exact query, total count, DOIs, and quota information. |
search_literature(query, limit=10, cursor="*", max_chars=10000) |
One Europe PMC page with abstracts and DOI/PMCID deduplication. |
resolve_article(identifier, max_chars=10000) |
DOI/PMID/PMCID resolution, abstract, access status and OpenAlex OA links. |
get_article(identifier, max_chars=10000, include_text=True) |
Available Europe PMC OA XML as bounded article sections; otherwise metadata/abstract. |
get_article_section(identifier, section_id, offset=0, max_chars=10000) |
One section or a character slice, with next_offset for continuation. |
All tools publish explicit input and output schemas. Detailed records include a common
bibliography object while preserving legacy author/year fields. See the
data contracts for types, null semantics and compatibility.
See the user guide for search syntax, data provenance, rate limits, caching, text budgets and troubleshooting.
Architecture
flowchart LR
MCP[MCP tools] --> App[Application services]
App --> WoS[Clarivate Starter]
App --> PMC[Europe PMC]
App --> OA[OpenAlex]
The server factory owns its clients and closes them at shutdown. Provider clients validate responses before caching them. The adapters validate tool responses and expose schemas for client discovery. The architecture decision explains the service boundaries and client ownership.
Project status
GitHub Actions defines checks for Python 3.12 and 3.14, lint, type checking and installation from built artifacts. See the changelog for release and migration notes, and the release guide for distribution and verification.
For development setup and ordinary issues, see Contributing. For vulnerability reports, see the security policy.
License and data access
The code is licensed under Apache-2.0. See NOTICE. You can run the bridge yourself with your own provider credentials and entitlements. Provider API access and bibliographic metadata remain subject to their applicable terms. Article text carries its own license. Review that license before reusing the text, and confirm provider permissions before hosting the service for others or redistributing records. The repository provides the self-hosted bridge. A paid hosted service would require separate arrangements for credentials, quotas, data rights and support.
Metadata
Release files for wos-mcp-bridge 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wos_mcp_bridge-0.2.0.tar.gz | 193.3 kB | With provenance | Details for wos_mcp_bridge-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wos_mcp_bridge-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for wos_mcp_bridge-0.2.0-py3-none-any.whl |
Total release size: 238.2 kB
Release files / wos_mcp_bridge-0.2.0.tar.gz
| Download URL | wos_mcp_bridge-0.2.0.tar.gz |
|---|---|
| Size | 193.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cf180164fa287d24a85248c1c7142981937783abecd7cd9ffd58776a5d4033f
|
|
BLAKE2b-256 checksum How to use checksums |
a7a42249f67cf77e1e05fa534e200f01df22243552381087102582edbe2dffbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / wos_mcp_bridge-0.2.0-py3-none-any.whl
| Download URL | wos_mcp_bridge-0.2.0-py3-none-any.whl |
|---|---|
| Size | 44.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebc71152099c79db7602a9e91b478b6c150a341528281744f12279373f3dc644
|
|
BLAKE2b-256 checksum How to use checksums |
af91f8e97ee603805d62028b9344bb4cb4fb08bbbf20ee37dd41667d400895e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for wos-mcp-bridge 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for wos_mcp_bridge-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.