String Db Mcp Server

Created By
Augmented-Naturea year ago
A comprehensive Model Context Protocol (MCP) server for accessing the STRING protein interaction database. This server provides powerful tools for protein network analysis, functional enrichment, and comparative genomics through the STRING API.
Overview

What is STRING DB MCP Server?

STRING DB MCP Server is a comprehensive Model Context Protocol (MCP) server designed for accessing the STRING protein interaction database, providing tools for protein network analysis, functional enrichment, and comparative genomics through the STRING API.

How to use STRING DB MCP Server?

To use the STRING DB MCP Server, install the server using npm, configure it in your application, and utilize the provided API endpoints to perform various protein analysis tasks.

Key features of STRING DB MCP Server?

  • Access to protein interaction data and analysis tools.
  • Functional enrichment analysis using GO terms and KEGG pathways.
  • Comparative genomics tools for finding homologous proteins across species.
  • Robust error handling and support for multiple species.

Use cases of STRING DB MCP Server?

  1. Analyzing protein interactions for specific proteins.
  2. Performing functional enrichment analysis on protein sets related to diseases.
  3. Finding homologous proteins for evolutionary studies.
  4. Building and analyzing protein interaction networks for research.

FAQ from STRING DB MCP Server?

  • Can I access data for all known proteins?

Yes! The STRING DB MCP Server supports over 5000 organisms and provides extensive protein interaction data.

  • Is there a limit to the number of queries I can make?

The server has rate limiting in place to ensure fair usage, but you can make multiple queries as needed within those limits.

  • How often is the data updated?

The STRING database is regularly updated with new experimental data to ensure accuracy and relevance.

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