MCP Servers

Created By
pathintegral-institutea year ago
Open Source MCP Servers for Scientific Research
Overview

What is MCP Servers?

MCP Servers are open-source Message Control Protocol (MCP) servers designed for scientific research, enabling users to create and manage their own servers for various applications.

How to use MCP Servers?

To use MCP Servers, you can install them via PyPI, clone the latest main branch from GitHub, or use a specific branch. After installation, you can create and configure your own server package using provided commands and configurations.

Key features of MCP Servers?

  • Open-source and customizable server framework
  • Easy installation via PyPI or GitHub
  • Ability to create and manage multiple server instances
  • Logging and debugging support

Use cases of MCP Servers?

  1. Setting up custom servers for scientific data processing.
  2. Developing and testing new protocols in a controlled environment.
  3. Collaborating on research projects that require specific server configurations.

FAQ from MCP Servers?

  • Is MCP Servers free to use?

Yes! MCP Servers are open-source and free for everyone to use.

  • Can I contribute to MCP Servers?

Absolutely! Contributions are welcome, and you can follow the guidelines in the repository to submit your changes.

  • What programming language is used in MCP Servers?

MCP Servers are primarily developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pathintegral-institute
Star
2
Language
Python
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)

2 days ago