mocxykit

Created By
shunsevena year ago
This is an Frontend development service middleware that can be used with webpack and vite. Its main function is to visualize the configuration, manage http(s)-proxy, and mock data.
Overview

What is mocxykit?

mocxykit is a frontend development service middleware designed to visualize configurations, manage HTTP(S) proxies, and mock data, compatible with webpack and vite.

How to use mocxykit?

To use mocxykit, install it via npm with npm install mocxykit --save-dev, then configure it in your webpack or vite project as per the provided examples in the documentation.

Key features of mocxykit?

  • Visual management of mock data and proxy configurations
  • Support for global and custom URL proxies
  • Dynamic switching between proxy and mock data
  • Integration with Ngrok for public access
  • Support for multiple environment variable management

Use cases of mocxykit?

  1. Proxying requests during frontend development
  2. Mocking API responses for testing
  3. Visualizing and managing multiple proxy configurations
  4. Enabling public access to local development environments using Ngrok

FAQ from mocxykit?

  • Can mocxykit be used with any frontend framework?

Yes! mocxykit can be integrated with any project using webpack or vite.

  • Is mocxykit free to use?

Yes! mocxykit is open-source and free to use.

  • How does mocxykit handle mock data?

mocxykit allows you to define mock data responses based on request parameters and supports random data generation using faker.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shunseven
Star
32
Language
JavaScript
License
MIT 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