Skip to main content
Glama
carlosgutierrezch

Azure SQL MCP Server

by carlosgutierrezch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABASEYesThe name of the database
SERVER_NAMEYesThe Azure SQL server name (e.g., your-server.database.windows.net)
AZURE_CLIENT_IDNoOptional Azure client ID for authentication via environment variables
AZURE_TENANT_IDNoOptional Azure tenant ID for authentication via environment variables
AZURE_CLIENT_SECRETNoOptional Azure client secret for authentication via environment variables

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_database_configA

Check if the database is properly configured.

Returns configuration status and any error messages.
execute_queryC

Execute a SQL query against the Azure SQL database.

Args:
    query: SQL query to execute (e.g., "SELECT * FROM users LIMIT 10")
get_tablesA

Get list of all tables in the Azure SQL database.

get_table_schemaB

Get schema information for a specific table.

Args:
    table_name: Name of the table (e.g., "users" or "schema.table_name")
get_sample_dataA

Get sample data from a table.

Args:
    table_name: Name of the table (e.g., "users" or "schema.table_name")
    limit: Number of rows to return (default: 5, max: 100)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool serves a distinct function: config check, arbitrary query execution, listing tables, getting schema, and retrieving sample data. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (check_database_config, execute_query, get_sample_data, get_tables, get_table_schema), making the set predictable.

Tool Count5/5

Five tools cover essential database introspection and querying capabilities without unnecessary clutter, appropriate for a focused Azure SQL server.

Completeness4/5

Core operations are covered, but dedicated tools for data manipulation (insert/update/delete) or schema modification are missing, though these can be performed via execute_query. Minor gap.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources