Databases and Custom Tools
This area controls which user databases MCP keys can reach and which administrator-defined operations AI clients may invoke.
DB Management supports SQLite, PostgreSQL, MySQL, SQL Server, Oracle, and Firebird.
- Name the connection and select its SQL provider.
- Enter the provider-specific connection values.
- Test connectivity.
- Save the definition and assign it to an MCP key.
Credentials are encrypted at rest. These user-database connections are separate from the internal Admin/Auth database.
Use a custom tool when an operation should have an administrator-controlled structure instead of accepting arbitrary SQL from the AI client.
- Give the tool a clear name and description.
- Select query or DML behavior.
- Define its parameters and SQL definition.
- Parse, format, and test the definition.
- Save it and allow it on the appropriate MCP keys.
Custom query tools inherit table, row, timeout, and concurrency enforcement. Custom DML tools also use the server's DML policy and human MCP Elicitation flow.
Add human-readable table and column descriptions when database names alone do not convey business meaning. Schema discovery merges this metadata into the information returned to AI clients.
See MCP Tools Reference for runtime behavior and Security Governance for enforcement rules.