Enterprise Model Context Protocol (MCP) Server & Client

Created By
sanjay-sia year ago
MCP Client & Server
Overview

What is Enterprise Model Context Protocol (MCP)?

Enterprise MCP is a server and client implementation designed to connect large language models (LLMs) with enterprise tools and data sources, optimizing for cost and performance.

How to use Enterprise MCP?

To use Enterprise MCP, clone the repository, set up the server and client, and connect to the server using WebSocket. You can perform database queries, file operations, and API integrations through the MCP client.

Key features of Enterprise MCP?

  • Cost-Optimized: Zero-cost testing without LLM API keys.
  • Multi-LLM Support: Integrates with OpenAI and Anthropic models.
  • Security Features: JWT authentication and role-based access control.
  • Real-time Communication: WebSocket support for bidirectional communication.
  • Monitoring: Prometheus metrics for performance tracking.

Use cases of Enterprise MCP?

  1. Connecting LLMs to enterprise databases for analytics.
  2. Automating file operations in a secure environment.
  3. Integrating external APIs for enhanced functionality.

FAQ from Enterprise MCP?

  • Can I use Enterprise MCP without API keys?

Yes! It supports zero-cost testing without requiring LLM API keys.

  • What programming language is used?

The project is implemented in Python.

  • How do I deploy Enterprise MCP?

You can deploy it using Docker or Kubernetes for production environments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sanjay-si
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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)

a day ago