πŸš€ MCP Client-Server Repository

Created By
kaioobraboa year ago
An MCP Server that's also an MCP Client. Useful for letting Claude develop and test MCPs without needing to reset the application.
Overview

What is MCP Client-Server?

MCP Client-Server is a repository that contains an MCP Server which also functions as an MCP Client. It is designed to facilitate the development and testing of Model Context Protocols (MCPs) without the need to reset the application frequently.

How to use MCP Client-Server?

To use the MCP Client-Server, download the application from the provided link, launch the downloaded file, and start exploring the functionalities of both the MCP Server and Client.

Key features of MCP Client-Server?

  • Dual functionality as both an MCP Server and Client.
  • Streamlined development and testing process for MCPs.
  • Easy to download and set up for immediate use.

Use cases of MCP Client-Server?

  1. Developing and testing new MCPs without application resets.
  2. Facilitating collaboration among developers working on MCPs.
  3. Enhancing the efficiency of the MCP development workflow.

FAQ from MCP Client-Server?

  • Is the MCP Client-Server free to use?

Yes! The MCP Client-Server is free to use for all developers.

  • What programming languages does MCP Client-Server support?

The MCP Client-Server is primarily developed in TypeScript and supports various SDKs.

  • How can I contribute to the MCP Client-Server?

You can fork the repository, make changes, and submit pull requests to enhance its functionality.

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

13 minutes ago