Warp SQL Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryC | Execute a SQL query on the connected SQL Server database |
| list_databasesA | List all databases on the SQL Server instance |
| list_tablesB | List all tables in a specific database |
| describe_tableC | Get the schema information for a specific table |
| list_foreign_keysC | List all foreign key relationships in a schema |
| get_table_dataB | Get sample data from a table with optional filtering and limiting |
| export_table_csvC | Export table data in CSV format |
| get_performance_statsB | Get overall performance statistics and health summary |
| get_query_performanceC | Get detailed query performance breakdown by tool |
| get_connection_healthB | Get connection pool health metrics and diagnostics |
| explain_queryC | Get the execution plan for a SQL query to analyze performance |
| analyze_query_performanceC | Analyze query performance and provide optimization suggestions |
| get_index_recommendationsC | Get index recommendations for database optimization |
| detect_query_bottlenecksC | Detect and analyze query bottlenecks in the database |
| get_optimization_insightsC | Get comprehensive database optimization insights and health analysis |
| get_server_infoC | Get MCP server configuration, status, and logging information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Several performance-related tools significantly overlap: analyze_query_performance, detect_query_bottlenecks, get_query_performance, get_performance_stats, and get_optimization_insights all target similar diagnostic territory with unclear boundaries. Schema and data tools are distinct, but the clustering of performance tools creates real ambiguity for an agent.
The tool names overwhelmingly follow a snake_case verb_noun pattern (list_tables, execute_query, export_table_csv). Minor inconsistency exists because verbs vary widely (describe, list, get, analyze, detect, export), but the pattern remains predictable and readable.
At 16 tools, the server sits right at the upper edge of an appropriate scope. The count is not unreasonable for a SQL Server MCP, but the redundancy among performance-analysis tools makes the set feel heavier than necessary.
The core SQL Server workflows are covered: schema exploration, query execution, sample data retrieval, CSV export, and performance diagnostics. Execute_query provides a general escape hatch for missing write operations, though there is no explicit tool for DDL or data modification.