Which integrations are available for this server?

Integrates with GitHub Copilot in VS Code Agent mode to provide database analysis and query capabilities, including schema discovery, query execution, and health analysis.

How do I use DB Analyzer MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@DB Analyzer MCP Server Run a schema health check for the Northwind database" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

DB Analyzer MCP Server

by FusionGuy

Overview Schema Related Servers Score Discussions

JavaScript

Remote

DB Analyzer MCP Server

A Model Context Protocol (MCP) server that provides comprehensive SQL Server database analysis and query capabilities for AI assistants like Claude.

Features

This MCP server exposes 10 powerful tools for database analysis and management:

Connection & Testing

ping_db - Test database connectivity and retrieve server information

Query Execution

execute_query - Execute SELECT queries with optional row limits
execute_non_query - Execute DDL/DML statements (CREATE, UPDATE, DELETE, etc.)
execute_stored_procedure - Call stored procedures with typed parameters

Schema Discovery

list_databases - List all databases with optional name filtering
list_schemas - List schemas in a specific database
list_tables - List tables with optional schema/name filtering
get_table_columns - Get detailed column information including types, constraints, and primary keys
get_indexes - Retrieve index information for specific tables

Health Analysis

analyze_schema_health - Comprehensive database health check including:
- Tables without clustered indexes (heaps)
- Tables missing primary keys
- Usage of deprecated data types (text, ntext, image, sql_variant)
- Wide tables (configurable column threshold)
- Unused indexes based on usage statistics
- Missing index suggestions from SQL Server DMVs
- Fragmented indexes (>30% fragmentation, >1000 pages)

Related MCP server: MSSQL Database MCP Server

Installation

Prerequisites

Node.js (v18 or higher recommended)
Access to a SQL Server instance
npm or yarn package manager

Setup

Clone the repository:

git clone https://dev.azure.com/goplanet-west/West%20AI/_git/mcp-db-analyzer
cd mcp-db-analyzer

Install dependencies:
```
npm install
```
Build the project:
```
npm run build
```

Configuration

Environment Variables

The server supports the following environment variables for database connection:

Variable	Description	Default
`DB_HOST`	SQL Server hostname	`<database-hostname>`
`DB_USER`	Database username	`<database-user>`
`DB_PASSWORD`	Database password	`<database-password>`
`DB_DATABASE`	Default database (optional)	None
`DB_PORT`	SQL Server port	`1433`
`DB_ENCRYPT`	Enable connection encryption	`true`
`DB_TRUST_SERVER_CERT`	Trust server certificate	`true`
`DB_POOL_MAX`	Maximum connection pool size	`10`

MCP Client Configuration

Claude Desktop

Add the following to your Claude Desktop configuration file:

Windows: %APPDATA%\Claude\claude_desktop_config.json macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "db-analyzer": {
      "command": "node",
      "args": ["C:\\MCP-Servers\\db-analyzer\\build\\index.js"],
      "env": {
        "DB_HOST": "your-server.database.windows.net",
        "DB_USER": "your-username",
        "DB_PASSWORD": "your-password",
        "DB_PORT": "1433",
        "DB_ENCRYPT": "true",
        "DB_TRUST_SERVER_CERT": "false"
      }
    }
  }
}

Cline (VS Code Extension)

Add to your Cline MCP settings:

{
  "mcpServers": {
    "db-analyzer": {
      "command": "node",
      "args": ["C:\\MCP-Servers\\db-analyzer\\build\\index.js"],
      "env": {
        "DB_HOST": "your-server.database.windows.net",
        "DB_USER": "your-username",
        "DB_PASSWORD": "your-password"
      }
    }
  }
}

Visual Studio Code (GitHub Copilot)

VS Code supports MCP servers natively through GitHub Copilot's Agent mode (VS Code 1.99+).

Option 1 — Workspace configuration (checked into source control, applies to everyone opening this project):

Create or edit .vscode/mcp.json in your project root:

{
  "servers": {
    "db-analyzer": {
      "command": "node",
      "args": ["C:\\MCP-Servers\\db-analyzer\\build\\index.js"],
      "env": {
        "DB_HOST": "your-server.database.windows.net",
        "DB_USER": "your-username",
        "DB_PASSWORD": "your-password",
        "DB_PORT": "1433",
        "DB_ENCRYPT": "true",
        "DB_TRUST_SERVER_CERT": "false"
      }
    }
  }
}

Option 2 — User settings (applies to all your VS Code projects):

Open your user settings.json (Ctrl/Cmd+Shift+P → Preferences: Open User Settings (JSON)) and add:

{
  "mcp": {
    "servers": {
      "db-analyzer": {
        "command": "node",
        "args": ["C:\\MCP-Servers\\db-analyzer\\build\\index.js"],
        "env": {
          "DB_HOST": "your-server.database.windows.net",
          "DB_USER": "your-username",
          "DB_PASSWORD": "your-password",
          "DB_PORT": "1433",
          "DB_ENCRYPT": "true",
          "DB_TRUST_SERVER_CERT": "false"
        }
      }
    }
  }
}

Activating the server:

Open the Copilot Chat panel (Ctrl/Cmd+Alt+I)
Switch to Agent mode using the mode selector at the bottom of the chat input
Click the Tools button (⚙) to verify db-analyzer appears in the tool list
Start chatting — Copilot will automatically invoke the MCP tools as needed

Note: If the server doesn't appear, run MCP: List Servers from the Command Palette to refresh, and check the output panel for errors.

Other MCP Clients

For other MCP-compatible clients (Cursor, Continue, etc.), refer to their documentation for adding custom MCP servers. The general pattern is:

Command: node (or full path to Node.js)
Arguments: Path to build/index.js
Environment: Database connection variables

Usage Examples

Once connected to an MCP client, you can use natural language to interact with your database:

Example Prompts

Connection Testing:

"Test the database connection and show me the server version"

Schema Discovery:

"Show me all databases on this server"
"List all tables in the dbo schema"
"What are the columns in the Users table?"

Data Querying:

"Get the first 10 rows from the Orders table"
"Show me all customers from California"

Health Analysis:

"Analyze the database for potential issues"
"Find all tables without primary keys"
"Show me any fragmented indexes"

Development

Project Structure

db-analyzer/
├── src/
│   └── index.ts           # Main server implementation
├── build/                 # Compiled JavaScript (generated)
├── node_modules/          # Dependencies (generated)
├── package.json           # Project metadata and dependencies
├── tsconfig.json          # TypeScript configuration
├── .gitignore            # Git ignore rules
└── README.md             # This file

Scripts

npm run build - Compile TypeScript to JavaScript
npm start - Run the compiled server

Making Changes

Edit src/index.ts
Run npm run build to compile
Restart your MCP client to load changes

Security Considerations

⚠️ Important Security Notes:

Credentials: Never commit database credentials to version control. Use environment variables or secure credential storage.
Connection Encryption: For production databases, set DB_ENCRYPT=true and DB_TRUST_SERVER_CERT=false.
Permissions: Use a database account with minimal required permissions. Consider read-only access if write operations aren't needed.
Network Security: Ensure your SQL Server is not exposed to the public internet. Use VPNs or private networks when possible.
SQL Injection: The server uses parameterized queries where possible, but be cautious with dynamic SQL in custom queries.

Connection Pool Management

The server maintains connection pools per database to optimize performance. Pools are automatically created on first use and cleaned up on server shutdown. Connection parameters:

Max connections: 10 (configurable via DB_POOL_MAX)
Idle timeout: 30 seconds
Automatic reconnection on connection loss

Troubleshooting

Common Issues

Connection Refused:

Verify SQL Server is running and accessible
Check firewall rules allow connections on port 1433
Ensure SQL Server authentication is enabled if using username/password

Login Failed:

Verify credentials are correct
Check user has appropriate database permissions
For Windows Authentication, use appropriate connection string format

Certificate Errors:

For self-signed certificates, set DB_TRUST_SERVER_CERT=true
For production, obtain proper SSL certificates

MCP Server Not Appearing:

Verify the path to build/index.js is correct
Check Node.js is installed and accessible
Review MCP client logs for error messages

License

[Specify your license here]

Contributing

[Specify contribution guidelines here]

Support

For issues and questions:

Create an issue in the Azure DevOps repository
Contact your development team

Available Tools

10 tools

analyze_schema_healthD

ParametersJSON Schema

Name	Required	Description	Default
`database`	No
`wideTableMinColumns`	No	Minimum column count to consider a table 'wide'

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

execute_non_queryD

ParametersJSON Schema

Name	Required	Description	Default
`sql`	Yes	T-SQL batch (DDL/DML)
`database`	No	Database context

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

execute_queryD

ParametersJSON Schema

Name	Required	Description
`sql`	Yes	T-SQL text to execute
`database`	No	Database context
`rowLimit`	No	Optional limit using SET ROWCOUNT

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

execute_stored_procedureD

ParametersJSON Schema

Name	Required	Description
`params`	No	Procedure parameters
`database`	No	Database context
`procedure`	Yes	Stored procedure name, optionally schema-qualified

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_indexesD

ParametersJSON Schema

Name	Required	Description	Default
`table`	Yes
`schema`	Yes
`database`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_table_columnsD

ParametersJSON Schema

Name	Required	Description	Default
`table`	Yes
`schema`	Yes
`database`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_databasesD

ParametersJSON Schema

Name	Required	Description	Default
`nameLike`	No	Optional name filter, e.g., %Prod%

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_schemasD

ParametersJSON Schema

Name	Required	Description	Default
`database`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_tablesD

ParametersJSON Schema

Name	Required	Description
`schema`	No
`database`	No
`tableLike`	No	Optional table name filter with % wildcard

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

ping_dbD

ParametersJSON Schema

Name	Required	Description	Default
`database`	No	Database name to connect to (optional)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

10 tool updatesv0.1.0Aug 2, 2026
- First observedanalyze_schema_health
- First observedexecute_non_query
- First observedexecute_query
- First observedexecute_stored_procedure
- First observedget_indexes
- First observedget_table_columns
- First observedlist_databases
- First observedlist_schemas
- First observedlist_tables
- First observedping_db

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.1/5.0

Disambiguation4/5

Tool names clearly indicate distinct operations: ping for connectivity, query vs non-query for different statement types, stored procedure for SP calls, and list/get for schema introspection. Minor ambiguity exists between execute_query and execute_non_query, but they are standard distinct categories.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., ping_db, execute_query, list_tables, get_indexes). No mixed conventions or vague verbs.

Tool Count5/5

The server has 10 tools, which is well within the ideal range for a database analyzer. Each tool covers a clear aspect of database interaction and introspection, earning its place without bloat.

Completeness4/5

The tool surface covers essential database operations: connectivity, query execution, schema object listing (databases, schemas, tables, columns, indexes), and schema health analysis. Minor gaps like constraint or foreign key introspection exist, but core analysis and execution workflows are well represented.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Dot - AI Data AnalystOAuth
io.github.zurferr
Ask data questions in natural language. Get SQL, insights, and charts from your databases.
Search Databases Data Visualization
2
Cayra Decision IntelligenceOAuth
io.cayra
Ask questions in plain language, get answers from your business database. No SQL required.
1
QueryBearOAuth
io.github.spencerpauly
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Databases RAG Systems
2
Databricks B
io.github.mcp-dir
Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu
Data Platforms Databases
171

Related MCP Servers

Microsoft SQL Server MCP
Databases Search
NicolasPirello
A
license
Not graded
quality
D
maintenance
Enables AI assistants to connect and query Microsoft SQL Server databases using natural language, executing read-only SQL queries for safe data inspection and analysis.
Updated 9 months ago (2025-12-10 17:33 UTC)
MIT
MSSQL Database MCP Server
Databases Developer Tools
vpro1032
A
license
Not graded
quality
D
maintenance
Enables AI assistants to securely interact with Microsoft SQL Server databases to query data, inspect schemas, and retrieve metadata with read-only operations by default and optional write capabilities.
Updated 9 months ago (2025-12-07 22:22 UTC)
1
MIT
SQL Server MCP Server
Databases Developer Tools
Nebhg
F
license
Not graded
quality
D
maintenance
Enables AI assistants to interact with SQL Server databases through natural language, providing capabilities for executing queries, exploring schemas, analyzing performance, backing up tables, and managing data with built-in safety limits.
Updated a year ago (2025-06-27 20:48 UTC)
-
Database MCP Server
Databases Developer Tools
hadi21k
A
license
Not graded
quality
B
maintenance
Enables AI assistants to safely query and explore SQL Server and PostgreSQL databases with read-only access, supporting schema discovery, relationship exploration, and query execution.
Updated 2 months ago (2026-07-14 11:42 UTC)
37
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FusionGuy/mcp-db-analyzer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server