Chembl Mcp Server

Created By
Augmented-Naturea year ago
A comprehensive Model Context Protocol (MCP) server providing advanced access to the ChEMBL chemical database. This server offers 22 specialized tools enabling AI assistants and MCP clients to perform sophisticated drug discovery research, chemical informatics analysis, and bioactivity investigations directly through ChEMBL's REST API.
Overview

What is Chembl MCP Server?

Chembl MCP Server is a comprehensive Model Context Protocol (MCP) server that provides advanced access to the ChEMBL chemical database, enabling sophisticated drug discovery research, chemical informatics analysis, and bioactivity investigations through its REST API.

How to use Chembl MCP Server?

To use the Chembl MCP Server, you can clone the repository, install the necessary dependencies, and run the server. It can also be integrated with MCP clients for seamless communication.

Key features of Chembl MCP Server?

  • 22 specialized tools for various chemical and biological analyses.
  • Core functionalities include compound search, target analysis, and bioactivity data retrieval.
  • Advanced search capabilities and batch processing for efficiency.
  • Docker support for easy deployment.

Use cases of Chembl MCP Server?

  1. Conducting drug discovery research by analyzing compounds and their bioactivity.
  2. Performing chemical informatics analysis to retrieve detailed compound and target information.
  3. Integrating with AI assistants for automated drug discovery workflows.

FAQ from Chembl MCP Server?

  • What types of analyses can I perform?

    You can perform compound searches, target analyses, bioactivity measurements, and more using the provided tools.

  • Is there a cost to use the Chembl MCP Server?

    No, the server is open-source and free to use.

  • How can I contribute to the project?

    You can fork the repository, create a feature branch, and submit a pull request with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Augmented-Nature
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago