io.github.cyanheads/pubchem-mcp-server

Public Hosted Server: https://pubchem.caseyjhand.com/mcp

Tools

Eight tools for querying PubChem's chemical information database:

pubchem_search_compounds

Search PubChem for chemical compounds across five search modes.

• Identifier lookup — resolve compound names, SMILES, or InChIKeys to CIDs (batch up to 25)
• Formula search — find compounds by molecular formula in Hill notation
• Substructure/superstructure — find compounds containing or contained within a query structure
• 2D similarity — find structurally similar compounds by Tanimoto similarity (configurable threshold)
• Optionally hydrate results with properties to avoid a follow-up details call

pubchem_get_compound_details

Get detailed compound information by CID.

• Batches up to 100 CIDs in a single request
• 27 available properties: molecular weight, SMILES, InChIKey, XLogP, TPSA, complexity, stereo counts, and more
• Optionally includes textual descriptions (pharmacology, mechanism, therapeutic use) from PUG View
• Optionally includes all known synonyms (trade names, systematic names, registry numbers)
• Optionally computes drug-likeness assessment (Lipinski Rule of Five + Veber rules) from fetched properties
• Optionally fetches pharmacological classification (FDA classes, mechanisms of action, MeSH classes, ATC codes)

pubchem_get_bioactivity

Get a compound's bioactivity profile from PubChem BioAssay.

• Returns assay outcomes (Active/Inactive/Inconclusive), target info (protein accessions, NCBI Gene IDs), and quantitative values (IC50, EC50, Ki)
• Filter by outcome to focus on active results
• Caps at 100 results per request (well-studied compounds may have thousands)

pubchem_get_summary

Get descriptive summaries for four PubChem entity types.

• Assays (AID), genes (Gene ID), proteins (UniProt accession), taxonomy (Tax ID)
• Up to 10 entities per call
• Type-specific field extraction for clean, structured output

Features

Built on @cyanheads/mcp-ts-core:

• Declarative tool definitions — single file per tool, framework handles registration and validation
• Unified error handling across all tools
• Pluggable auth (none, jwt, oauth)
• Swappable storage backends: in-memory, filesystem, Supabase, Cloudflare KV/R2/D1
• Structured logging with optional OpenTelemetry tracing
• Runs locally (stdio/HTTP) or containerized via Docker

PubChem-specific:

• Rate-limited client for PUG REST and PUG View APIs (5 req/s with automatic queuing)
• Retry with exponential backoff on 5xx errors and network failures
• All tools are read-only and idempotent — no API keys required

Getting Started

Public Hosted Instance

A public instance is available at https://pubchem.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:

{
  "mcpServers": {
    "pubchem": {
      "type": "streamable-http",
      "url": "https://pubchem.caseyjhand.com/mcp"
    }
  }
}

Self-Hosted / Local

Add to your MCP client config (e.g., claude_desktop_config.json):

{
  "mcpServers": {
    "pubchem": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/pubchem-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio"
      }
    }
  }
}

Prerequisites

• Bun v1.2.0 or higher (or Node.js v22+)

Installation

1. Clone the repository:

git clone https://github.com/cyanheads/pubchem-mcp-server.git

1. Navigate into the directory:

cd pubchem-mcp-server

1. Install dependencies:

bun install

Configuration

No API keys are required — PubChem's API is freely accessible.

Running the Server

Local Development

• Build and run the production version:

  bun run build
  bun run start:http   # or start:stdio
  

• Run in dev mode (auto-reload):

  bun run dev:stdio    # or dev:http
  

• Run checks and tests:

  bun run devcheck     # Lints, formats, type-checks
  bun run test         # Runs test suite
  

Docker

docker build -t pubchem-mcp-server .
docker run -p 3010:3010 pubchem-mcp-server

Project Structure

Development Guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

• Handlers throw, framework catches — no try/catch in tool logic
• Use ctx.log for domain-specific logging
• Register new tools in the index.ts barrel file

Contributing

Issues and pull requests are welcome. Run checks before submitting:

bun run devcheck
bun run test

License

Apache-2.0 — see LICENSE for details.