Gomcp MCP Server

If you want an AI assistant working directly with Gomcp, the gomcp mcp server is the bridge. :warning: This project was a first experiment to expose an MCP for Lightpanda Browser. But now, the browser embed an MCP server natively. More details in the native MCP blog post.

What Gomcp does

:warning: This project was a first experiment to expose an MCP for Lightpanda Browser. But now, the browser embed an MCP server natively. More details in the native MCP blog post.

Tools it exposes

Once connected, the assistant can call this tool directly:

• Requirements — gomcp requires you to have already installed Lightpanda Browser

Installing the gomcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

gomcp requires you to have already installed Lightpanda Browser.

Where it fits

Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. Gomcp sits in that group, and the shape of its toolset — Requirements — tells you what it is really for. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by lightpanda-io, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the gomcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.