🤖 Hamibot MCP Server

Created By
hamibota year ago
用于与 Hamibot API 进行交互。它提供了一系列工具来管理和控制 Hamibot 设备及脚本
Overview

What is Hamibot MCP Server?

Hamibot MCP Server is a server implementation based on the Model Context Protocol (MCP) designed for interacting with the Hamibot API. It provides a suite of tools for managing and controlling Hamibot devices and scripts.

How to use Hamibot MCP Server?

To use Hamibot MCP Server, install it via npm and set up your access token. You can then configure it to work with your applications, such as Claude Desktop, by adding the necessary configuration to your JSON files.

Key features of Hamibot MCP Server?

  • Device management: List all connected devices.
  • Script management: View and run automation scripts.
  • Code execution: Execute custom JavaScript code on specified devices.
  • Variable passing: Pass custom parameters to scripts.

Use cases of Hamibot MCP Server?

  1. Managing multiple Hamibot devices from a single interface.
  2. Automating tasks using custom scripts.
  3. Executing JavaScript code for advanced device control.

FAQ from Hamibot MCP Server?

  • How do I install Hamibot MCP Server?

You can install it using npm with the command: npm install -g @hmbt/hamibot-mcp-server.

  • What is the purpose of the access token?

The access token is required to authenticate your requests to the Hamibot API.

  • Can I run custom scripts on my devices?

Yes! You can create and run custom automation scripts on your connected devices.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hamibot
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago