@mcplookup-org/mcp-server

Created By
MCPLookup-orga year ago
MCP Bridge Server - Universal MCP client with dynamic discovery and tool management
Overview

What is MCP Server?

MCP Server is a universal MCP client that facilitates dynamic discovery and management of various MCP servers, eliminating the need for hardcoded server configurations.

How to use MCP Server?

To use MCP Server, install it via npm and run it with your API key. You can operate it in standard input/output mode or as an HTTP server.

Key features of MCP Server?

  • Dynamic discovery of MCP servers without hardcoding.
  • Management tools for installing, controlling, and monitoring MCP servers.
  • Docker support for secure server isolation and management.

Use cases of MCP Server?

  1. Connecting AI agents to multiple MCP servers dynamically.
  2. Managing server lifecycles and health monitoring.
  3. Facilitating tool invocation across different servers.

FAQ from MCP Server?

  • Can MCP Server connect to any MCP server?

Yes! It can dynamically discover and connect to any MCP server.

  • Is there Docker support?

Yes! MCP Server includes comprehensive Docker support for secure isolation.

  • How do I get my API key?

You can obtain your API key from the MCPLookup dashboard.

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