MCP Midscene MCP Server

Proyecto de automation con Playwright e inteligencia artificial (Midscene).

Local serverstdio

What is the MCP Midscene MCP server?

If you already use MCP Midscene, the mcp midscene mcp server is the piece that lets your assistant work with it directly. Proyecto de automation con Playwright e inteligencia artificial (Midscene).

Available tools

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

  • aiTap — Operación de clic
  • aiHover — Operación de hover (pasar el cursor)
  • aiInput — Operación de entrada de texto
  • aiKeyboardPress — Operación de teclado
  • aiScroll — Operación de desplazamiento
  • aiQuery — Consulta a IA
  • aiAssert — Aserción de IA
  • aiWaitFor — Espera basada en IA

Credentials and setup notes

Configuration is passed through the environment: MIDSCENE_MODEL_NAME, OPENAI_API_KEY, MCP_SERVER_REQUEST_TIMEOUT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as playwright, 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.

Where it fits

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Midscene's toolset — aiTap, aiHover, aiInput and 5 more — is a fair guide to whether it matches your workflow. It is maintained by MauroCor; worth a glance at recent repository activity before you build anything load-bearing on it.

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

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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
aiTapOperación de clic
aiHoverOperación de hover (pasar el cursor)
aiInputOperación de entrada de texto
aiKeyboardPressOperación de teclado
aiScrollOperación de desplazamiento
aiQueryConsulta a IA
aiAssertAserción de IA
aiWaitForEspera basada en IA

How to install the MCP Midscene MCP server

{
  "mcpServers": {
    "midscene": {
      "command": "npx",
      "args": ["-y", "playwright"],
      "env": {
        "MIDSCENE_MODEL_NAME": "your-value",
        "OPENAI_API_KEY": "your-value",
        "MCP_SERVER_REQUEST_TIMEOUT": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MIDSCENE_MODEL_NAMEConfiguration value read at startup.Optional
OPENAI_API_KEYCredential the server authenticates with.Yes
MCP_SERVER_REQUEST_TIMEOUTConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Midscene to aiTap.
  • Use MCP Midscene to aiHover.
  • Use MCP Midscene to aiInput.

Frequently asked questions

It connects MCP Midscene to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (aiTap, aiHover, aiInput, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Midscene directly.