My Coding Buddy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List all databases in the MySQL server. Returns: str: A formatted string containing all database names, one per line |
| list_tablesA | List all tables in the current database. Returns: str: A formatted string containing all table names, one per line |
| list_viewsA | List all views in the current database. Returns: str: A formatted string containing all view names, one per line |
| search_tablesA | Search for tables and views matching a pattern. Args: pattern (str): Search text or wildcard expression Returns: str: Matching table and view names, one per line |
| list_columnsA | List columns for a given table. Args: table_name (str): Table name to inspect Returns: str: Column names and types for the table |
| get_table_schemaA | Get the schema information for a specific table. Args: table_name (str): Name of the table to get schema for Returns: str: A formatted string containing the table schema information Each column's information is on a new line Raises: Error: If the table doesn't exist or schema retrieval fails |
| get_table_indexesB | Get index information for a specific table. Args: table_name (str): Table name to inspect Returns: str: Index metadata for the table |
| get_table_createA | Get the CREATE TABLE statement for a specific table. Args: table_name (str): Table name to inspect Returns: str: The DDL statement used to create the table |
| get_table_row_countC | Get the approximate row count for a table. Args: table_name (str): Table name to inspect Returns: str: Row count information |
| execute_queryA | Execute a SQL query and return the results as a formatted string. Args: query (str): The SQL query to execute Returns: str: A formatted string representation of the query results Each row is on a new line, with columns separated by tabs Raises: Error: If the query execution fails |
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 10 tools
Most tools have distinct purposes, but get_table_schema and list_columns both return column info, causing some overlap. Other tools like execute_query and get_table_create are clearly different.
All tool names follow a consistent verb_noun pattern (e.g., list_tables, get_table_schema, execute_query), with no mixing of styles.
10 tools is well-scoped for a database MCP server, covering essential operations without being bloated or insufficient.
The set covers query execution, schema inspection, and listing of objects. Data modification is possible via execute_query, but dedicated tools for common DML are missing. Slight gap in table-level information like row count already present.