floorp

Floorp MCP Server acts as a bridge between AI assistants and the Floorp browser, exposing capabilities to interact with Floorp programmatically. The server enables listing and creating tabs, retrieving browser history and downloads, accessing page content (HTML or text), and performing automation actions such as clicking elements, navigating pages, and filling forms. Once the server is running, you can connect your MCP client to floorp and issue structured commands that map to these browser actions, allowing AI agents to browse and automate tasks within Floorp without manual interaction.

To use it, start the server via npx as instructed in the usage section. The server exposes its capabilities through the MCP protocol, so your client can request actions like opening a new tab, listing existing tabs, fetching the current page content, and triggering automation steps (click, navigate, fill). Ensure Floorp is running and that the mcp feature is enabled in Floorp's settings (floorp.mcp.enabled must be true in about:config) before starting the MCP server. When configuring your MCP client, point it at the floorp server named in your mcp_config and use the supported commands to perform browser operations through the AI assistant.

Prerequisites:

• Floorp browser installed and running
• Node.js installed (for npx usage)
• Floorp MCP feature enabled in Floorp (set floorp.mcp.enabled to true in about:config)

Installation steps:

1. Verify prerequisites

• Ensure Floorp is running and the MCP feature is enabled in Floorp settings.
• Install Node.js from https://nodejs.org if not already installed.

2. Run the MCP server using npx (recommended)

npx -y floorp-mcp-server

3. Optional: run from a local clone (if you prefer installing locally)

git clone <repository-url-for-floorp-mcp-server>
cd floorp-mcp-server
npm install
npx floorp-mcp-server

4. Configure your MCP client to connect to the floorp server with the following mcp_config snippet:

{
  "mcpServers": {
    "floorp": {
      "command": "npx",
      "args": ["-y", "floorp-mcp-server"]
    }
  }
}

5. Optional environment configuration If you need to set environment notes for the server, you can pass environment variables (example shown in the mcp_config):

"env": {
  "FLOORP_MCP_ENABLED": "Set floorp.mcp.enabled to true in Floorp about:config"
}

Note: The exact repository URL and package name may vary; use the npm package name floorp-mcp-server as referenced in the usage section.

Tips and common issues:

• Ensure Floorp is running and accessible before starting the MCP server.
• The Floorp MCP feature must be enabled in Floorp's about:config (floorp.mcp.enabled = true).
• If you encounter connection issues, verify that Floorp is not blocked by firewall and that the MCP server command is available in your PATH when using npx.
• You can run the server in the background or as a service if your environment supports it, but ensure you manage its lifecycle so it remains reachable by your MCP client.
• When debugging, check Floorp logs and the MCP server console output for any errors related to tab management, history access, or automation actions.
• In environments with multiple browsers or profiles, ensure the Floorp instance you intend to automate is the one Floorp MCP Server connects to.