MCP Registry & Tester

Created By
Preetnagdaa year ago
Application to test your MCP servers. Register, manage and test all in one place.
Overview

What is MCP Registry & Tester?

MCP Registry & Tester is a Next.js application designed for registering and testing Model Context Protocol (MCP) servers, allowing users to manage their MCP servers efficiently.

How to use MCP Registry & Tester?

To use the application, clone the repository, install dependencies, set up a PostgreSQL database, configure environment variables, and run the development server. Access the application at http://localhost:3000.

Key features of MCP Registry & Tester?

  • Register MCP servers with custom URLs and headers.
  • List and manage all registered MCP servers.
  • Connect to MCP servers and discover their tools.
  • Test MCP tools with custom arguments.
  • Support for multiple transport protocols (stdio, HTTPS/Streamable HTTP).

Use cases of MCP Registry & Tester?

  1. Registering and managing multiple MCP servers in one interface.
  2. Testing tools on MCP servers with various configurations.
  3. Developing and debugging local and remote MCP servers.

FAQ from MCP Registry & Tester?

  • Can I register multiple MCP servers?

Yes! You can register as many MCP servers as you need.

  • What transport protocols are supported?

The application supports stdio and Streamable HTTP protocols.

  • Is there a database requirement?

Yes, a PostgreSQL database is required to store server configurations.

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