MCP Project

Created By
ourdigitala year ago
MCP servers and clients sandbox
Overview

what is MCP Project?

MCP Project is a collection of Message Control Protocol (MCP) servers and clients designed for local AI applications, enabling seamless communication and control.

how to use MCP Project?

To use MCP Project, set up the Git MCP module by following the instructions in the module's README. This allows you to execute Git commands through a REST API.

key features of MCP Project?

  • Git MCP module for handling Git operations via REST API
  • Easy execution of Git commands
  • Convenient client library for managing repositories

use cases of MCP Project?

  1. Integrating Git operations into AI applications
  2. Automating version control tasks in local environments
  3. Facilitating communication between AI components using MCP

FAQ from MCP Project?

  • What is the purpose of the MCP Project?

The MCP Project aims to provide a standardized way for AI applications to communicate and control various operations through the Message Control Protocol.

  • How can I contribute to the MCP Project?

Contributions are welcome! Please check the project's GitHub repository for guidelines on how to contribute.

  • Is there documentation available for the MCP Project?

Yes! Detailed documentation can be found in the README files of each module.

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