trackmcp
Back to directory
wavelovey

pubmed_search

View on GitHub

MCP PubMed Search Server

46 stars PythonServers & Infrastructure Updated Oct 23, 2025

Documentation

pubmed_search MCP server

search pubmed via MCP

Components

Resources

The server implements a simple note storage system with:

  • Custom note:// URI scheme for accessing individual notes
  • Each note resource has a name, description and text/plain mimetype

Prompts

The server provides a single prompt:

  • summarize-notes: Creates summaries of all stored notes
    • Optional "style" argument to control detail level (brief/detailed)
    • Generates prompt combining all current notes with style preference

Tools

The server implements one tool:

  • add-note: Adds a new note to the server
    • Takes "name" and "content" as required string arguments
    • Updates server state and notifies clients of resource changes

Configuration

[TODO: Add configuration details specific to your implementation]

Quickstart

Install

Claude Desktop

On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`

On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

Development/Unpublished Servers Configuration

code
"mcpServers": {
    "pubmed_search": {
      "command": "uv",
      "args": [
        "--directory",
        "/Users/nofuture/Documents/GitHub/pubmed_search",
        "run",
        "pubmed_search"
      ]
    }
  }

Published Servers Configuration

code
"mcpServers": {
    "pubmed_search": {
      "command": "uvx",
      "args": [
        "pubmed_search"
      ]
    }
  }

Development

Building and Publishing

To prepare the package for distribution:

1. Sync dependencies and update lockfile:

bash
uv sync

2. Build package distributions:

bash
uv build

This will create source and wheel distributions in the `dist/` directory.

3. Publish to PyPI:

bash
uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: `--token` or `UV_PUBLISH_TOKEN`
  • Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging

experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via `npm` with this command:

bash
npx @modelcontextprotocol/inspector uv --directory /Users/nofuture/Documents/GitHub/pubmed_search run pubmed-search

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

Frequently asked questions

What is pubmed_search?

pubmed_search is MCP PubMed Search Server

How do I install pubmed_search?

Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.

Is pubmed_search open source?

Yes — it is hosted on GitHub at https://github.com/wavelovey/pubmed_search and has 46 stars.

Related MCP tools

Run your own MCP server? See who uses it and what to fix.

Measure it with TrackMCP