"Improving Cursor Efficiency and Smart Features" matching MCP servers:

Enables MCP clients to execute SELECT-only SQL against a music-store schema with statement timeouts, guardrails, and retry/reflection support.

Enables managing Databricks directly from Cursor IDE with 30 tools for notebooks, clusters, jobs, DBFS, SQL, and workspace operations.

Enables natural language querying of any SQL database by converting plain English questions into SQL queries, with auto-schema detection and safety features.

MCP server that provides predictive inventory analysis tools to AI agents, including current stock, sales velocity, and replenishment alerts.

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

Enables querying, searching, and analyzing Cursor IDE conversation history from SQLite workspaceStorage databases. Supports exporting chat data in multiple formats and provides workspace utilities for managing conversation data across projects.

MCP server for querying hydroponic sensor data stored in PostgreSQL/TimescaleDB. Provides tools to list tables, describe schemas, read recent sensor readings, fetch latest data, and perform time-series aggregations via natural language.

A Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.

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

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.

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 discover and invoke CRUD tools and read-only resources for generated services, allowing direct interaction with the same data exposed by the REST API.

It enables AI assistants to discover and invoke CRUD operations as MCP tools and read application data through MCP resources, allowing natural-language interaction with the generated backend.

It enables LLMs to interact with generated REST APIs by exposing CRUD operations as MCP tools and readable records as MCP resources. This lets AI clients discover and manage API data through the Model Context Protocol.

Enables LLMs to discover and invoke CRUD operations and read-only data resources for generated services through the Model Context Protocol, alongside traditional REST endpoints.

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

Enables users to ask plain-English questions against MySQL, PostgreSQL, SQLite, SQL Server, Oracle, and MariaDB databases by auto-detecting schemas and converting requests into safe, read-only SQL queries.

Enables LLMs and AI assistants to discover and use tools and resources for CRUD operations on generated services, providing direct interaction with the same data exposed by REST endpoints.

A Model Context Protocol server that connects AI tools to Electronic Health Records using SMART on FHIR, allowing secure searching, querying, and analysis of patient data from compatible EHRs.