"A device or tool to control Home Assistant" matching MCP servers:

Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.

A specialized MCP server for detailed control of Home Assistant lights, supporting advanced features like RGB colors, color temperatures, effects, and robust scene management. It includes specific fixes for IKEA Tradfri devices and intentionally focuses on lights only to ensure home safety.

MCP server that gives AI coding assistants the ability to see and interact with mobile devices. 49 tools for Android/iOS — AI-powered visual analysis (Claude + Gemini), smart tap/type by description, Flutter widget tree inspection, video recording, and test script generation. 4-tier element search with <1ms local matching. Free tier included, zero setup via npx.

Enables controlling a real iPhone or iPad over USB for app development testing, including building and installing apps, launching with console logs, inspecting the accessibility tree, tapping, swiping, typing, taking screenshots, managing app files, and recording audio.

Semantic navigator for MCP tools that finds relevant tools by natural language intent, reducing token usage by 95%.

Enables coding assistants to drive iOS Simulators and Android emulators or USB devices for React Native and Expo work, including taking screenshots, reading app and device logs, opening deep links, installing builds, and launching or relaunching apps. It also supports Android-specific actions such as adb reverse for Metro, opening the dev menu, and tapping or typing on screen.

A starter MCP server for running local tools and resources on a home machine or NAS, enabling secure access from AI assistants like Kody.

MCP server for foldkit, exposing the 7-prime spine, 7 κ-bands, and 6 fold operations as native tools and resources for use in any MCP client.

Exposes the host device's current date and time, returning local time with timezone offset or UTC.

Enables AI models to perform comprehensive Git repository management including cloning, file operations, branching, committing, and pushing changes via a secure FastMCP interface. It features built-in workspace isolation and rigorous input validation to ensure production-ready repository control.

A Model Context Protocol server that provides a scratchpad tool for LLMs to organize thoughts, take notes, and plan approaches to complex problems.

MCP router that fronts your other MCP servers behind a few small generic tools, so their tool definitions stay out of the context window and are discovered on demand.

A tool discovery MCP server that integrates with Azure DevOps wikis and code-graph-rag to match natural language goals to tools, enabling tool composition and proxy testing.

Encoding-aware, indentation-smart file tools for AI coding agents. 20+ tools including read/edit with automatic encoding detection, smart indentation conversion, SSH, SFTP, process management, and system utilities.

Portable governance control-promotion CLI and MCP server.

A simple MCP server implementation in TypeScript that communicates over stdio, allowing users to ask questions that end with 'yes or no' to trigger the MCP tool in Cursor.

A server built on mcp-framework that enables integration with Claude Desktop through the Model Context Protocol.

Enables an AI assistant to set up and maintain a smart-home instance by adding integrations through config flows, editing registries, and building or debugging automations, scripts, scenes, helpers, dashboards, and blueprints. It also covers diagnostics, repairs, trace inspection, and backup management, with read-only and confirmation safeguards.

Provides a unified MCP server to interact with multiple middleware (Loki, MySQL, Redis, RocketMQ, Elasticsearch, MongoDB) through a desktop application for connection management and configuration export.

Turns any OpenAPI spec into a single-tool MCP server where the model writes JavaScript against a typed api object in a QuickJS sandbox, so multi-step tasks run in one round trip and only the final result reaches context. Credentials, rate limiting, retries, write gating and audit logging stay on the host, outside the sandbox.