Skip to main content

Model Context Protocol server for Zotero

Project description

Model Context Protocol server for Zotero

GitHub branch status PyPI - Version

This project is a python server that implements the Model Context Protocol (MCP) for Zotero, giving you access to your Zotero library within AI assistants. It is intended to implement a small but maximally useful set of interactions with Zotero for use with MCP clients.

Zotero Server MCP server

Features

This MCP server provides the following tools:

  • zotero_search_items: Search for items in your Zotero library using a text query
  • zotero_item_metadata: Get detailed metadata information about a specific Zotero item
  • zotero_item_fulltext: Get the full text of a specific Zotero item (i.e. PDF contents)

These can be discovered and accessed through any MCP client or through the MCP Inspector.

Each tool returns formatted text containing relevant information from your Zotero items, and AI assistants such as Claude can use them sequentially, searching for items then retrieving their metadata or text content.

Installation

This server can either run against either a local API offered by the Zotero desktop application) or through the Zotero Web API. The local API can be a bit more responsive, but requires that the Zotero app be running on the same computer with the API enabled. To enable the local API, do the following steps:

  1. Open Zotero and open "Zotero Settings"
  2. Under the "Advanced" tab, check the box that says "Allow other applications on this computer to communicate with Zotero".

[!IMPORTANT] For access to the /fulltext endpoint on the local API which allows retrieving the full content of items in your library, you'll need to install a Zotero Beta Build (as of 2025-03-30). Once 7.1 is released this will no longer be the case. See https://github.com/zotero/zotero/pull/5004 for more information. If you do not want to do this, use the Web API instead.

To use the Zotero Web API, you'll need to create an API key and find your Library ID (usually your User ID) in your Zotero account settings here: https://www.zotero.org/settings/keys

These are the available configuration options:

  • ZOTERO_LOCAL=true: Use the local Zotero API (default: false, see note below)
  • ZOTERO_API_KEY: Your Zotero API key (not required for the local API)
  • ZOTERO_LIBRARY_ID: Your Zotero library ID (your user ID for user libraries, not required for the local API)
  • ZOTERO_LIBRARY_TYPE: The type of library (user or group, default: user)

uvx with Local Zotero API

To use this with Claude Desktop and a direct python install with uvx, add the following to the mcpServers configuration:

{
  "mcpServers": {
    "zotero": {
      "command": "uvx",
      "args": ["--upgrade", "zotero-mcp"],
      "env": {
        "ZOTERO_LOCAL": "true",
        "ZOTERO_API_KEY": "",
        "ZOTERO_LIBRARY_ID": ""
      }
    }
  }
}

The --upgrade flag is optional and will pull the latest version when new ones are available. If you don't have uvx installed you can use pipx run instead, or clone this repository locally and use the instructions in Development below.

Docker with Zotero Web API

If you want to run this MCP server in a Docker container, you can use the following configuration, inserting your API key and library ID:

{
  "mcpServers": {
    "zotero": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e", "ZOTERO_API_KEY=PLACEHOLDER",
        "-e", "ZOTERO_LIBRARY_ID=PLACEHOLDER",
        "ghcr.io/kujenga/zotero-mcp:main"
      ],
    }
  }
}

To update to a newer version, run docker pull ghcr.io/kujenga/zotero-mcp:main. It is also possible to use the docker-based installation to talk to the local Zotero API, but you'll need to modify the above command to ensure that there is network connectivity to the Zotero application's local API interface.

Development

Information on making changes and contributing to the project.

  1. Clone this repository
  2. Install dependencies with uv by running: uv sync
  3. Create a .env file in the project root with the environment variables above

Start the MCP Inspector for local development:

npx @modelcontextprotocol/inspector uv run zotero-mcp

To test the local repository against Claude Desktop, run echo $PWD/.venv/bin/zotero-mcp in your shell within this directory, then set the following within your Claude Desktop configuration

{
  "mcpServers": {
    "zotero": {
      "command": "/path/to/zotero-mcp/.venv/bin/zotero-mcp"
      "env": {
        // Whatever configuration is desired.
      }
    }
  }
}

Running Tests

To run the test suite:

uv run pytest

Docker Development

Build the container image with this command:

docker build . -t zotero-mcp:local

To test the container with the MCP inspector, run the following command:

npx @modelcontextprotocol/inspector \
    -e ZOTERO_API_KEY=$ZOTERO_API_KEY \
    -e ZOTERO_LIBRARY_ID=$ZOTERO_LIBRARY_ID \
    docker run --rm -i \
        --env ZOTERO_API_KEY \
        --env ZOTERO_LIBRARY_ID \
        zotero-mcp:local

Relevant Documentation

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

iflow_mcp_zotero_mcp-0.1.6.tar.gz (28.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

iflow_mcp_zotero_mcp-0.1.6-py3-none-any.whl (10.7 kB view details)

Uploaded Python 3

File details

Details for the file iflow_mcp_zotero_mcp-0.1.6.tar.gz.

File metadata

File hashes

Hashes for iflow_mcp_zotero_mcp-0.1.6.tar.gz
Algorithm Hash digest
SHA256 71d7bd0600581bcb4612fe11493047e89ceeeb244df2ddbd2124f148800895a2
MD5 0b7793a87571d619e5c9dc724b12c835
BLAKE2b-256 1e24e72899a0100bb066c141d74e3c5bd136cbc5995e73f399397f6437587ff2

See more details on using hashes here.

File details

Details for the file iflow_mcp_zotero_mcp-0.1.6-py3-none-any.whl.

File metadata

File hashes

Hashes for iflow_mcp_zotero_mcp-0.1.6-py3-none-any.whl
Algorithm Hash digest
SHA256 4702ff4e430b1708b0b2649e57c44c293b81a5803fd2d19694f95c0e7a2827a3
MD5 a07efe86263b96be518f0fcbf1dcc416
BLAKE2b-256 70f82f7f1bb229c8e50574f38b4a1c219c7c7d8901a18afcda707f24df4f0615

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page