MCP Registry Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Registry Server?

MCP Registry Server is a tool designed to retrieve MCP (Multi-Channel Protocol) servers using semantic search capabilities.

how to use MCP Registry Server?

To use the MCP Registry Server, you need to install it via Smithery, build the server, and configure it in your Claude Desktop setup.

key features of MCP Registry Server?

  • MCP Retriever: Allows users to retrieve MCP servers using semantic search.
  • Installation via Smithery: Simplifies the installation process for users.
  • Configuration for Claude Desktop: Provides a clear guide on how to integrate with Claude Desktop.

use cases of MCP Registry Server?

  1. Retrieving specific MCP servers based on user queries.
  2. Integrating MCP server functionalities into applications using Claude Desktop.
  3. Facilitating semantic search for better server discovery.

FAQ from MCP Registry Server?

  • How do I install the MCP Registry Server?

You can install it using the command: npx -y @smithery/cli install @KBB99/mcp-registry-server --client claude.

  • Can I modify the MCP Registry Server?

Yes! It is licensed under the MIT License, allowing you to use, modify, and distribute the software.

  • What is the main functionality of the MCP Registry Server?

The main functionality is to retrieve MCP servers using semantic search.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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