Bluetooth MCP Server

Created By
Hypijump31a year ago
bluetooth-mcp-server for Claude AI
Overview

What is Bluetooth MCP Server?

Bluetooth MCP Server is a Model Context Protocol server designed for Claude AI and other AI assistants to detect and interact with Bluetooth devices in the vicinity.

How to use Bluetooth MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the server. You can then expose it to the internet and configure Claude to use it for scanning Bluetooth devices.

Key features of Bluetooth MCP Server?

  • Multi-protocol scanning for BLE and Classic Bluetooth devices
  • Flexible filtering options for device detection
  • Automatic recognition of common devices
  • Enhanced information retrieval about devices
  • Cross-platform support for Windows, macOS, and Linux
  • Seamless integration with Claude AI

Use cases of Bluetooth MCP Server?

  1. Scanning for nearby Bluetooth devices using Claude AI.
  2. Identifying and categorizing Bluetooth devices in various environments.
  3. Enhancing AI interactions with real-world Bluetooth device data.

FAQ from Bluetooth MCP Server?

  • What are the requirements to run the server?

    You need Python 3.7+, a Bluetooth adapter, and admin/sudo privileges for some operations.

  • Can I use this server on any operating system?

    Yes! It supports Windows, macOS, and Linux.

  • How do I troubleshoot Bluetooth issues?

    Ensure Bluetooth is enabled, run with admin privileges, and check for discoverable devices.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Hypijump31
Star
1
Language
Python
License
MIT 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