ChEMBL-MCP-Server

Created By
BioMCP-Huba year ago
Overview

what is ChEMBL-MCP-Server?

ChEMBL-MCP-Server is a FastMCP wrapper server that provides API access to the ChEMBL database, allowing users to interact with chemical data efficiently.

how to use ChEMBL-MCP-Server?

To use ChEMBL-MCP-Server, clone the repository, install the dependencies, and start the server using the provided commands. You can specify parameters such as host, port, and transport method.

key features of ChEMBL-MCP-Server?

  • Complete API access to the ChEMBL database
  • Asynchronous API calls using FastMCP framework
  • Built-in error handling and timeout mechanisms
  • Support for both HTTP and stdio transport methods
  • Complete type annotations and docstrings

use cases of ChEMBL-MCP-Server?

  1. Accessing chemical activity data for research purposes.
  2. Converting chemical representations (e.g., SMILES to InChI).
  3. Integrating chemical data into applications for drug discovery.

FAQ from ChEMBL-MCP-Server?

  • What is the ChEMBL database?

The ChEMBL database is a large-scale bioactivity database for drug discovery.

  • How can I install ChEMBL-MCP-Server?

You can install it by cloning the repository and running the installation commands provided in the documentation.

  • What transport methods are supported?

The server supports both HTTP and stdio transport methods.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BioMCP-Hub
Star
0
Language
Jupyter Notebook
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago