MCP Server settings

Start Here

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

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History 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 Console Model Context Protocol endpoint and API keys used by compatible MCP clients. This lets approved tools query estate-wide Mini DBA performance and historical monitoring data through the console.

What you can see

MCP Endpoint URL.
Managed MCP API keys stored by the console.
A 14-day trial key button where trial access is enabled.
Copy buttons for the endpoint and newly-created keys.
Key revoke controls where available.
Available MCP tools exposed by the console endpoint.

Manage MCP keys

Open Settings.
Select MCP Server.
Copy the MCP endpoint URL into your MCP client configuration.
Create a 14-day trial key, or sign in as console administrator and create a persistent key.
Copy the new key immediately. Mini DBA stores only a salted hash and cannot show the raw key again.
Paste the key into the MCP client's bearer-token/API-key setting.

Managed keys are stored in mcp-api-keys.json beside minidba-engines.json. This file is the only supported MCP key store, so trial access, persistent keys, rotation, and revocation all use the same path.

Trial keys expire after 14 days by default. Persistent keys do not expire until revoked.

Rate limiting

The console rate-limits MCP requests per API key before the request reaches the MCP tool layer. Trial keys default to 30 requests per minute. Persistent keys default to 300 requests per minute. When a key exceeds its limit, the console returns HTTP 429 Too Many Requests with a Retry-After header.

Rate limits are held in memory by the running console process. This is suitable for the current single-instance console/App Service deployment. If the console is scaled out to multiple instances, use a shared limiter such as Redis or another distributed store so the same key is limited globally across every instance.

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.
Use trial keys for demo users and short evaluations, not for long-running automation.

MCP access guidance

The console MCP endpoint allows approved clients to query Mini DBA monitoring data across connected engines. 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, console status, engine connection status, firewall rules, web proxy requirements, and Service Log. Remove keys that are no longer in use.