MCP Server Settings

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

MCP Server settings expose the Mini DBA Model Context Protocol endpoint and API keys used by compatible MCP clients. This lets approved tools query Mini DBA performance and historical monitoring data.

What You Can See

MCP Endpoint URL.
Existing API keys, masked for safety.
Copy buttons for endpoint and keys.
New key entry.
Key delete controls where available.

Manage MCP Keys

Open Settings.
Select MCP Server.
Copy the MCP endpoint URL into your MCP client configuration.
Copy an existing API key or add a new key.
Save changes where applicable.
Restart the engine if the page indicates changes take effect after restart.

Security Recommendations

Treat MCP API keys like credentials.
Create separate keys per client where possible.
Remove keys that are no longer used.
Avoid sharing keys in tickets, screenshots, chat, or documentation.

MCP Access Guidance

The MCP Server endpoint allows approved clients to query Mini DBA monitoring data. Use it only for trusted tools and users who should have access to database performance and history. Create separate API keys per client or automation where possible so unused access can be removed without disrupting everything.

Before enabling an MCP client, confirm the network path, endpoint URL, key storage method, and data exposure policy. Monitoring data may include server names, database names, query text, timings, and operational history. Treat that data as sensitive, especially in customer or production environments.

If a client cannot connect, check the endpoint URL, API key, engine status, firewall rules, web proxy requirements, and Service Log. Remove keys that are no longer in use.