SQL Agent MCP Servers

Find MCP servers for schema inspection, query drafting, warehouse context, and database-aware agent workflows.

서버 비교SQL agents 검색

일치하는 MCP 서버

별도의 토픽 데이터베이스 없이 기존 MCP Servers 디렉터리에서 가져옵니다.

모든 검색 결과 보기
Postgres MCP Server
Provides secure database access to PostgreSQL using the Kysely ORM.
서버 보기
PostgreSQL Full Access MCP Server
A full-access PostgreSQL server for MCP with read/write capabilities and enhanced schema metadata.
서버 보기
PostgreSQL MCP Server
An MCP server that provides tools to interact with PostgreSQL databases.
서버 보기
PostgreSQL MCP Server
Provides read-only access to PostgreSQL databases using a connection string.
서버 보기
PostgreSQL MCP Server
A Kotlin-based MCP server for interacting with PostgreSQL databases.
서버 보기
PostgreSQL MCP Server
An MCP server for exploring and querying PostgreSQL databases.
서버 보기
PostgreSQL MCP Server
A server for managing PostgreSQL databases, enabling comprehensive database operations.
서버 보기
PostgreSQL MCP Server by CData
A read-only MCP server for PostgreSQL, enabling LLMs to query live data from PostgreSQL databases.
서버 보기
Supabase MCP
공식
Official Supabase MCP server for managing Supabase projects, databases, auth, storage, edge functions, and SQL workflows from AI agents.
서버 보기
Supabase Coolify MCP Server
Comprehensive MCP server for managing self-hosted Supabase on Coolify with full deployment, migrations, edge functions, and rollback support.
서버 보기
Supabase MCP Server
An MCP server providing administrative control over a Supabase PostgreSQL database, compatible with Cursor's Composer and Codeium's Cascade.
서버 보기
Supabase MCP Server
A server for querying and managing data in a Supabase database.
서버 보기

SQL Agent MCP가 맞는 곳

Give agents schema context and query assistance while building backend or analytics workflows.

Draft SQL, inspect tables, and reason about relationships from an MCP-compatible client.

Connect development, staging, or warehouse data with scoped access and review.

설정 체크리스트

  1. 1Choose a server that supports your SQL engine, hosted database, or warehouse.
  2. 2Create read-only credentials for exploration and query-drafting workflows.
  3. 3Add connection strings or environment variables to the MCP client configuration.
  4. 4Test against development or staging before connecting sensitive production data.

선택 방법

  • Prefer read-only access for schema inspection and query assistance.
  • Check whether the server supports result limits, table descriptions, query execution, and connection scoping.
  • Use production credentials only with approval, logging, and a rollback path.

SQL Agent MCP FAQ

Why use the SQL agent framing?

This topic focuses on the workflow: agents using schema context and SQL tools to help with backend, analytics, and data tasks.

Can SQL Agent MCP change data?

Some servers can execute write queries if credentials allow it. Use read-only credentials by default and require review for mutations.

Should I connect production data?

Start with local, development, or staging databases. If production access is necessary, use least-privilege credentials and explicit approvals.