browser-mcp

n8n nodes for Smart Browser Automation via MCP

Package Information

Downloads: 42 weekly / 1,844 monthly
Latest Version: 0.1.17
Author: Ejaz Ullah

Available Nodes

Browser Tool icon
Browser Tool
Connects to an Browser MCP server

Documentation

n8n Nodes — Browser Smart Automation ⚡

n8n-nodes-browser-smart-automation — n8n nodes for Smart Browser Automation via MCP.

🚀 Quick Start

Prerequisites:

  • Node.js (>= 18)
  • npm

Install dependencies:

npm install

Build the nodes:

npm run build

Run tests:

npm test

Lint the code:

npm run lint

For development (watch TypeScript):

npm run dev

📁 Project Structure

Top-level:

  • nodes/ — TypeScript source for each n8n node group
    • McpClientEX/ — client node
    • McpClientToolEX/ — tool node
    • McpTriggerEX/ — trigger node
    • shared/ — shared utilities, types and helpers
  • dist/ — built artifacts (included in files for publishing)
  • package.json — scripts and metadata
  • tsconfig.json, tsup.config.ts, jest.config.js, gulpfile.js

🧩 Included Nodes

  • McpClientEX — core MCP client integration
  • McpClientToolEX — helper tool utilities for MCP
  • McpTriggerEX — trigger node for MCP events

After building, the compiled nodes are available under dist/ and referenced in package.json for n8n consumption.

⚙️ Usage

Install and build the project, then copy the dist folder into your n8n custom nodes directory, or publish the package to npm and install it into your n8n instance. Restart n8n after adding new nodes.

If you want to run a single node's tests:

npx jest nodes/McpClientEX --runInBand

🛠 Development Notes

  • Building: npm run build (uses tsup).
  • Tests: npm test (uses jest).
  • Linting: npm run lint (eslint over nodes/).

Tips:

  • Keep shared code in nodes/shared/ and add tests in __test__ folders next to the code.
  • Use tsc --watch (via npm run dev) for fast iteration on types.

🤝 Contributing

Contributions are welcome. Please:

  1. Create an issue describing the change or feature.
  2. Open a branch with a descriptive name.
  3. Add tests for new behavior and ensure all tests pass.
  4. Create a pull request and reference the issue.

📜 License

This project is licensed under the MIT License — see package.json for details.

If you want, I can add CI instructions, badges, or a contributing checklist next. 💡

Discussion