skysql-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKYSQL_API_KEY | Yes | Your SkySQL API key |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_agentsA | List all available SkySQL DB agents with their capabilities |
| launch_serverless_dbC | Launch a new Serverless DB instance in SkySQL |
| delete_dbC | Delete a DB instance from SkySQL |
| ask_agentB | Ask a question to a specific DB agent |
| get_db_credentialsB | Get the credentials for a SkySQL database instance |
| update_ip_allowlistC | Update the IP allowlist for a SkySQL database instance with the current IP |
| list_servicesA | List all available SkySQL database services |
| execute_sqlC | Execute SQL query on a SkySQL database instance and return the results |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| launch_db_prompt | Create a prompt for launching a new serverless DB |
| delete_db_prompt | Create a prompt for deleting a DB |
| ask_agent_prompt | Create a prompt for asking questions to DB agents |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are mostly distinct, covering agent interactions and database lifecycle management. The only slight overlap is between list_agents and list_services, but the entity types (agents vs services) are clearly different, reducing selection risk.
All tool names follow a consistent verb_noun pattern (list, launch, delete, ask, get, update, execute), with no mixed conventions or unclear verbs. The naming is predictable and readable.
With 8 tools, the server is well-scoped for its purpose, balancing database operations with agent interaction without redundancy or unnecessary bloat.
Core database lifecycle is covered (launch, delete, list, credentials, SQL execution), plus agent interaction. Minor gaps exist, such as lack of explicit service status checks or credential rotation, but these are not critical for the main workflows.