ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

MCP server adds stored procedure, function, and trigger introspection tools

Six new MCP tools expose stored procedures, user-defined functions, and database triggers as queryable objects — three list tools and three detail tools — extending schema introspection beyond tables and views.

This release adds six tools to the MCP server that expose database procedural objects as first-class introspectable entities. Stored procedures, user-defined functions, and triggers each gain a list tool that enumerates the objects present in a given schema and a detail tool that returns the full object definition — parameter signatures, body text, and trigger event bindings where applicable. The pattern matches the existing table and view introspection tools, giving MCP clients a consistent interface across all database object types.

New introspection tools

  • Stored procedure list and detail. The list tool returns procedure names, schemas, and parameter counts; the detail tool returns the full parameter list with types, the procedure body, and the owning database.
  • User-defined function list and detail. The list tool enumerates functions by schema and return type; the detail tool returns the function signature, body, and determinism flag, with aggregate or window-function metadata where the engine supports it.
  • Trigger list and detail. The list tool returns trigger names alongside the table and event (INSERT, UPDATE, DELETE) they respond to; the detail tool returns the full trigger body and its execution timing (BEFORE, AFTER, INSTEAD OF).

Design consistency

  • Uniform list/detail pattern. Each object type follows the same two-tool split used by the existing table and view tools, so MCP clients that handle those tools can extend their handling to procedural objects with minimal additional logic.
  • Cross-database scope. All six tools operate against the set of databases connected to the platform runtime; callers specify which database to query as a parameter rather than connecting separately per database.

The tools appear in the MCP server's tool list immediately after upgrade with no configuration required. They complement the schema resource additions shipped in the same sprint and are designed for AI-assisted development workflows where a language model inspects database structure to generate queries or validate assumptions.

See the feature →

← All posts