Lynx DevTool MCP is a Model Context Protocol (MCP) server that lets coding agents control, operate and preview Lynx pages.
Add the following config to your MCP client:
Follow the configure MCP guide using the standard config from above. You can also install the Lynx DevTool MCP server using the Codex CLI:
Follow the MCP install guide, with the standard config from above. You can also install the Lynx DevTool MCP server using the VS Code CLI:
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.
Install the Lynx DevTool MCP server using the Gemini CLI.
Project wide:
Globally:
Alternatively, follow the MCP guide and use the standard config from above.
Using the Lynx DevTool MCP server is just like using DevTool.
You need to connect to the devices and open Apps like LynxExplorer.
Just like the "Elements" tab in DevTool,
there are various tools (prefixed with CSS_* or DOM_*) in Lynx DevTool MCP server to help you inspect the element tree.
All these tools are read-only. Modify the source code to make changes to the element tree.
Just like the "Console" tab in DevTool, the coding agent may use Lynx DevTool MCP server to read all the message in Console and their stack traces.
Just like the "Sources" tab in DevTool, all the loading JavaScript sources can be read by the Lynx DevTool MCP server.
This is useful for coding agent to find the corresponding code in Console stack traces.
The coding agent may also interact with the Lynx page using Lynx DevTool MCP server, performing actions like tap or drag.
The Lynx DevTool MCP server also provides tools to take screenshot of the current Lynx page. Using a multimodal model to understand the screenshot.