dmc-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DMC_COOKIE | Yes | 腾讯云控制台Cookie,从浏览器复制 | |
| DMC_MC_GTK | No | csrfCode,用于实例搜索,可选 |
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 |
|---|---|
| set_cookieA | Set or update the Tencent Cloud console cookie. AI can obtain this from the browser via Chrome DevTools MCP: document.cookie Then pass the full cookie string here. The mc_gtk (csrfCode) value is required for cluster search (DescribeClusters API). AI can extract it from the browser's performance API: performance.getEntriesByType('resource') .find(e => e.name.includes('csrfCode=')) ?.name.match(/csrfCode=(\d+)/)?.[1] If not provided, DMC login/SQL tools will still work (they don't require mc_gtk to be valid), but find_instance_by_ip will fail. Args: cookie: Full cookie string from the Tencent Cloud console browser tab. mc_gtk: Optional csrfCode value from the browser. Required for cluster search. |
| login_instanceA | Login to a database instance via Tencent Cloud DMC. Supports both TDSQL-C (CynosDB) and TDSQL (DCDB) instances. The session is cached - subsequent calls reuse the same token without re-login, unless the token expires. Use find_instance_by_ip to discover the instance_id and db_type, then pass the db_type value from the search results here. Args: instance_id: Instance ID, e.g. "cynosdbmysql-xxx" or "tdsqlshard-xxx" user: Database account name, e.g. "db_user" password: Database account password (plain text) db_type: Database type - "cynosdbmysql" (TDSQL-C) or "tdsql" (TDSQL) region_id: Region ID, default 4 (Shanghai) Returns: Login status message. |
| execute_selectA | Execute a SELECT query on a logged-in database instance. Only SELECT statements are allowed (enforced by SQL validation). Args: instance_id: Instance ID (must be logged in via login_instance first) sql: SELECT SQL statement to execute db_name: Target database name within the instance page_size: Max rows to return, default 50 Returns: Query results as formatted text. |
| list_databasesA | List all databases accessible by the current logged-in account on the specified instance. Args: instance_id: Instance ID (must be logged in) Returns: List of database names. |
| list_tablesC | List tables in a database, optionally filtered by name pattern. Args: instance_id: Instance ID (must be logged in) db_name: Database name search: Optional table name filter (fuzzy match) Returns: Table list with row counts and sizes. |
| get_table_detailA | Get detailed schema of a table: columns and DDL (CREATE TABLE statement). Args: instance_id: Instance ID (must be logged in) db_name: Database name table_name: Table name Returns: Column details and CREATE TABLE DDL. |
| list_active_sessionsA | List all currently active (logged-in) database instance sessions. Useful to check which instances are ready for querying. Returns: List of active instance IDs and their session status. |
| find_instance_by_ipA | Find a database instance by its internal Vip (proxy IP). Searches both TDSQL-C (CynosDB) and TDSQL (DCDB) instances. Typical workflow:
Args: ip: Internal Vip address, e.g. "10.0.0.1" region: Tencent Cloud region string, e.g. "ap-shanghai" (default), "ap-beijing", "ap-guangzhou". Must match the region where your cluster is deployed. Returns: Matching instance info (InstanceId, Name, Vip, DbType) or "not found". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/yangfeng20/dmc-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server