BioMed-MCP-Server

Created By
JackKuo666a year ago
A MCP Server for biomedical Literature Database
Overview

what is BioMed-MCP-Server?

BioMed-MCP-Server is a server designed to manage and provide access to a biomedical literature database, facilitating research and data retrieval in the biomedical field.

how to use BioMed-MCP-Server?

To use BioMed-MCP-Server, set up the server environment as per the documentation provided in the GitHub repository, and connect to the database to query biomedical literature.

key features of BioMed-MCP-Server?

  • Centralized access to a comprehensive biomedical literature database.
  • Efficient querying capabilities for research purposes.
  • Support for various biomedical literature formats.

use cases of BioMed-MCP-Server?

  1. Researchers can retrieve specific biomedical articles for their studies.
  2. Institutions can use the server to maintain a local database of biomedical literature.
  3. Developers can integrate the server with other applications for enhanced data access.

FAQ from BioMed-MCP-Server?

  • What type of literature can be accessed?

The server provides access to a wide range of biomedical literature, including research articles, reviews, and clinical studies.

  • Is there a user guide available?

Yes! A comprehensive user guide is available in the GitHub repository to assist with setup and usage.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
Star
0
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