Worker17

Created By
kortexa-aia year ago
An MCP server to monitor workers productivity and fire them as needed.
Overview

What is Worker17?

Worker17 is an MCP-enabled 3D Worker Monitoring and Control System designed to monitor worker productivity and manage their performance effectively.

How to use Worker17?

To use Worker17, set up the server and web application by following the development setup instructions or run it using Docker. You can also connect to the Worker17 MCP server using the MCP Inspector for real-time monitoring.

Key features of Worker17?

  • Real-time monitoring of worker status and position
  • Task assignment capabilities
  • Ability to terminate workers based on performance metrics
  • Integration with Claude Desktop for AI-assisted management

Use cases of Worker17?

  1. Monitoring the productivity of remote workers in real-time.
  2. Assigning tasks to workers based on their current status.
  3. Managing worker performance and taking necessary actions when performance is unsatisfactory.

FAQ from Worker17?

  • Is Worker17 suitable for all types of work environments?

Worker17 is primarily designed for environments where worker monitoring and control are essential, such as remote work settings.

  • Can I run Worker17 on my local machine?

Yes! You can run Worker17 locally by following the setup instructions provided in the documentation.

  • What technologies are used in Worker17?

Worker17 utilizes React, Three.js, Node.js, and WebSockets for its web application and server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kortexa-ai
Star
3
Language
TypeScript
License
MIT license
Category
monitoring
Tags

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