A Model Context Protocol (MCP) server for interacting with Zotero libraries
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-lrriver-zotero-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# zotero_mcp [English](./README.md) | [中文](./README_zh.md) Support connecting Zotero via MCP with a custom server and client, without the need for tools like the Claude app or Cursor. ## Environment configuration ``` conda create -n mcp python=3.12 -y conda activate mcp pip install -r requirements.txt ``` ## Run MCP First, create a `.env` file and fill in the following variables. `zotero_api_key` needs to be obtained from the Zotero official website, and `api_key` is your LLM's API key: ``` zotero_api_key='' api_key="" ``` First, create a `.env` file and fill in the following variables: ``` model="" llm_api_base = "" llm_api_key="" zotero_api_key='' library_id='' ``` `model` is the name of the LLM, `llm_api_base` is the URL of the LLM, and `llm_api_key` is the API Key for the LLM. The `zotero_api_key` can be created by visiting the [Zotero](https://www.zotero.org/settings/keys), and your [library_id](https://www.zotero.org/settings/keys) is shown below:  Then start the server: ```bash python ./server.py ``` Open a new terminal window and run the client: ```bash python ./client.py ``` Here's the testing result: Upload files in Zotero in advance:  Query document content via MCP: 
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.