Env Mcp

Created By
JackXuyia year ago
Overview

what is Env Mcp?

Env Mcp is a tool package designed to retrieve current environment system information across different platforms.

how to use Env Mcp?

To use Env Mcp, install it globally using npm and configure it in your MCP-supported application. You can then call various methods to get system information.

key features of Env Mcp?

  • Detailed system information retrieval
  • Cross-platform compatibility
  • Easy integration into MCP-supported applications
  • TypeScript type support

use cases of Env Mcp?

  1. Monitoring system performance metrics.
  2. Gathering hardware and software specifications for diagnostics.
  3. Integrating system information retrieval into applications for enhanced functionality.

FAQ from Env Mcp?

  • What platforms does Env Mcp support?

Env Mcp supports multiple platforms, ensuring broad compatibility.

  • Is Env Mcp easy to integrate?

Yes! Env Mcp is designed for easy integration into applications that support MCP.

  • Can I use Env Mcp in production?

Yes, Env Mcp is suitable for production use, provided it is configured correctly.

Server Config

{
  "mcpServers": {
    "env-mcp": {
      "name": "env-mcp",
      "type": "command",
      "command": "node",
      "args": [
        "/usr/local/lib/node_modules/@zhijianren/env-mcp/dist/index.js"
      ],
      "enabled": true,
      "autoApprove": [
        "env"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackXuyi
Star
-
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