test-multi-repo

Created By
devendershekhawata year ago
Test repository for multi-user GitHub MCP server
Overview

what is test-multi-repo?

Test-multi-repo is a test repository designed for a multi-user GitHub MCP (Multi-Channel Protocol) server, allowing multiple users to collaborate on projects using GitHub.

how to use test-multi-repo?

To use test-multi-repo, clone the repository from GitHub and start contributing by creating branches, making commits, and pushing changes.

key features of test-multi-repo?

  • Supports multi-user collaboration on GitHub.
  • Allows for version control and tracking of changes.
  • Facilitates testing of multi-channel protocols.

use cases of test-multi-repo?

  1. Collaborative software development among multiple users.
  2. Testing and validating multi-channel protocols in a controlled environment.
  3. Learning and practicing Git and GitHub workflows.

FAQ from test-multi-repo?

  • Can I contribute to test-multi-repo?

Yes! Contributions are welcome. Please follow the standard GitHub workflow for collaboration.

  • Is there any documentation available?

Documentation is available in the repository's README file.

  • What is the purpose of this repository?

The purpose is to provide a test environment for multi-user interactions on a GitHub MCP server.

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

2 days ago