Mocxykit MCP Server

This is an Frontend development service middleware that can be used with webpack and vite. Its main function is to visualize the configuration

Local serverstdio

What is the Mocxykit MCP server?

Connect Mocxykit to Claude, Cursor or any other MCP client and it stops being a tab you switch to. 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. The mocxykit mcp server is what makes that connection.

What the server does

export default defineConfig({ plugins: [ viteProxyMockPlugin({ apiRule: '/api/*', lang: 'zh', buttonPosition: 'bottom', // 可选:'top'(顶部)、'middle'(中间)、'bottom'(底部) 或坐标格式如 '100,100' }) ] }) ```

Installation

The server ships on npm as mocxykit, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • vite — export default defineConfig({ plugins: [ viteProxyMockPlugin({ apiRule: '/api/*', lang: 'zh', buttonPosition: 'bottom', //
  • express — app.use( proxyMockMiddleware({ // express-proxy-mock options }), );
  • Rsbuild — export default defineConfig({ // Rsbuild 配置 plugins: [ rsbuildProxyMockPlugin({ apiRule: '/api/*', lang: 'zh', buttonPosition: 'bottom', //

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mocxykit's toolset — vite, express, Rsbuild — is a fair guide to whether it matches your workflow. It is maintained by shunseven; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mocxykit's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
viteexport default defineConfig({ plugins: [ viteProxyMockPlugin({ apiRule: '/api/*', lang: 'zh', buttonPosition: 'bottom', // 可选:'top'(顶部)、'middle'(中间)、'bottom'(底部) 或坐标格式如 '100,100' }) ] })
expressapp.use( proxyMockMiddleware({ // express-proxy-mock options }), );
Rsbuildexport default defineConfig({ // Rsbuild 配置 plugins: [ rsbuildProxyMockPlugin({ apiRule: '/api/*', lang: 'zh', buttonPosition: 'bottom', // 可选:'top'(顶部)、'middle'(中间)、'bottom'(底部) 或坐标格式如 '100,100' }), ], });

How to install the Mocxykit MCP server

{
  "mcpServers": {
    "mocxykit": {
      "command": "npx",
      "args": ["-y", "mocxykit"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Mocxykit to vite.
  • Use Mocxykit to express.
  • Use Mocxykit to Rsbuild.

Frequently asked questions

It proxies requests and provides mock data to accelerate frontend development. It is designed for development only, not production.