MyRepoForControlup2

Created By
YanArada year ago
Repository for Controlup MCP Server Demo
Overview

what is MyRepoForControlup2?

MyRepoForControlup2 is a repository designed for demonstrating the Controlup MCP Server functionalities.

how to use MyRepoForControlup2?

To use this repository, clone it from GitHub and follow the instructions provided in the README file to set up the Controlup MCP Server demo.

key features of MyRepoForControlup2?

  • Provides a demo environment for Controlup MCP Server.
  • Includes sample configurations and scripts for easy setup.
  • Facilitates testing and learning about Controlup functionalities.

use cases of MyRepoForControlup2?

  1. Demonstrating the capabilities of Controlup MCP Server.
  2. Training new users on how to use Controlup.
  3. Testing configurations before deploying in a production environment.

FAQ from MyRepoForControlup2?

  • Is this repository official?

No, this repository is not an official Controlup repository.

  • How can I contribute to this project?

You can contribute by submitting issues or pull requests on GitHub.

  • Where can I find more information about Controlup?

You can visit the official Controlup website for more details.

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

a day ago