"Using AI to control and access data from Home Assistant and smart home devices" matching MCP servers:

MCP server that lets any LLM client query the Home Credit Default Risk SQLite database (307,511 loan applications) through 7 read-only tools, 4 resources, and 1 prompt over stdio, with natural language, SQL, and tool-calling interfaces.

Enables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.

Enables AI interaction with Microsoft Access and SQLite databases to perform SQL queries, updates, and data management. It supports importing and exporting data via CSV and Excel files and includes tools for managing human-readable notes about database files.

An MCP server that layers additional Home Assistant tools on top of voska/hass-mcp, enabling Lovelace dashboard management, automation/scene manipulation, SSH file access, and recorder database queries.

Search the fastest-growing US horse boarding directory: 6,000 facilities and 3,800 trainers across 48 states, plus boarding price data by state.

Enables chat, document search (RAG), and a declarative SQL tool builder over MCP so any client can use these capabilities.

Enables AI to interact with Microsoft Access (.mdb, .accdb) and SQLite 3 databases, including read-only support for Access 97 databases. Supports executing SQL queries, importing/export data from CSV and Excel files, and storing notes about database files.

Enables AI assistants to interact with generated REST APIs by discovering and using CRUD tools and read-only data resources.

Enables AI-powered interaction with Metabase instances and PostgreSQL databases through natural language. Creates models, SQL queries, metrics, and dashboards using both Metabase API and direct database connections.

Enables read- or write-scoped access to synthetic enterprise orders, inventory, support tickets, and metrics via schema-validated JSON-RPC tools over stdio and HTTP, with permission allow-lists and audit logging. It also exposes enterprise resources and prompt templates for grounded, cited, multi-step assistant workflows.

Enables LLMs to discover and invoke generated CRUD operations as MCP tools and read data through MCP resources, alongside standard REST endpoints, using one codebase.

Lets AI agents and developers inspect and query local MySQL, Redis, and MongoDB instances over STDIO or authenticated loopback HTTP, with read-only defaults and allowlisted non-production writes that require explicit opt-in. Production connections always reject writes, and database-enforced read-only accounts are recommended.

Enables LLM clients such as Cursor and Claude to discover and use generated REST services through MCP tools for create, update, and delete actions and MCP resources for list and get-by-id context. Services generated in one command are exposed simultaneously as REST endpoints and MCP tools and resources.

Enables AI assistants to discover and invoke CRUD tools and read-only resources over the Model Context Protocol for generated API services.

Enables AI assistants to interact directly with generated REST APIs by exposing CRUD operations as MCP tools and read-only data as resources.

Exposes generated CRUD services to LLM clients over the Model Context Protocol, providing tools for create, update, and delete actions plus read-only resources for listing and fetching records by id. It lets assistants like Claude, ChatGPT, and Cursor discover and manipulate the same data served by the project's REST endpoints without any extra glue code.

Exposes every generated CRUD service to LLM clients such as Claude, ChatGPT, or Cursor through discoverable MCP tools for create, update, and list actions plus read-only resources, so models can query and manipulate data without raw HTTP calls. It runs alongside the same codebase's REST endpoints, letting clients and AI share one data layer.

Enables LLMs to discover and invoke generated CRUD tools and resources, allowing AI assistants to interact with the same data exposed by the REST API. Supports MCP clients such as Cursor and Claude over HTTP.

Enables LLMs to discover and invoke generated API actions as MCP tools and read context through MCP resources for list and get-by-id operations. It provides HTTP-based MCP access for clients such as Cursor and Claude without extra glue code.

Enables LLMs to query real job data and summarize backend job failures using MCP tools backed by a SQLite database.