OMCP Manager

Created By
jinyalonga year ago
OMCP Manager is a package manager for Model Context Protocol (MCP) servers. It provides a simple command-line interface to manage MCP server packages, including installation, uninstallation, and configuration.
Overview

what is OMCP Manager?

OMCP Manager is a package manager designed for Model Context Protocol (MCP) servers, providing a command-line interface for managing MCP server packages, including installation, uninstallation, and configuration.

how to use OMCP Manager?

To use OMCP Manager, clone the repository, set up a virtual environment, install dependencies, and use the command-line interface to manage MCP packages.

key features of OMCP Manager?

  • List available MCP server packages
  • Install and uninstall MCP server packages
  • Manage package configurations
  • Support for multiple runtimes (Node.js, Python)
  • Client integration support (Claude, Cursor, etc.)

use cases of OMCP Manager?

  1. Managing packages for MCP servers in development environments.
  2. Automating the installation and configuration of MCP server packages.
  3. Facilitating collaboration among developers by managing dependencies.

FAQ from OMCP Manager?

  • What is the security warning regarding MCP tools?

MCP tools may pose potential poisoning risks; always verify the source and integrity of packages before installation.

  • How do I install OMCP Manager?

Clone the repository, create a virtual environment, install dependencies, and then install the package using pip.

  • Can I use OMCP Manager with different programming languages?

Yes, OMCP Manager supports multiple runtimes including Node.js and Python.

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

a day ago
Crevio

2 days ago