Skip to main content
Glama
abushadab

Self-Hosted Supabase MCP Server

by abushadab

get_database_connections

Retrieve details of active database connections from pg_stat_activity to monitor and manage database performance and usage in a self-hosted Supabase environment.

Instructions

Retrieves information about active database connections from pg_stat_activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the get_database_connections tool. It executes a SQL query on pg_stat_activity to retrieve details of active client backend database connections, casts certain fields to text, filters backend_type, orders by backend_start, and processes the result using shared utilities.
    execute: async (input: GetDbConnectionsInput, context: ToolContext) => {
        const client = context.selfhostedClient;
    
        // Query pg_stat_activity
        // Note: Access to pg_stat_activity might require superuser or specific grants.
        const getConnectionsSql = `
            SELECT
                pid,
                datname,
                usename,
                application_name,
                client_addr::text, -- Cast inet to text
                backend_start::text, -- Cast timestamp to text
                state,
                query
            FROM
                pg_stat_activity
            WHERE
                backend_type = 'client backend' -- Exclude background workers, etc.
                -- Optionally filter out self?
                -- AND pid != pg_backend_pid()
            ORDER BY
                backend_start
        `;
    
        const result = await executeSqlWithFallback(client, getConnectionsSql, true);
    
        return handleSqlResponse(result, GetDbConnectionsOutputSchema);
    },
  • Zod schemas for input (empty object), output (array of connection objects with fields like datname, usename, etc.), and static MCP input JSON schema (empty object).
    const GetDbConnectionsOutputSchema = z.array(z.object({
        datname: z.string().nullable().describe('Database name'),
        usename: z.string().nullable().describe('User name'),
        application_name: z.string().nullable().describe('Application name (e.g., PostgREST, psql)'),
        client_addr: z.string().nullable().describe('Client IP address'),
        backend_start: z.string().nullable().describe('Time when the backend process started'),
        state: z.string().nullable().describe('Current connection state (e.g., active, idle)'),
        query: z.string().nullable().describe('Last or current query being executed'),
        pid: z.number().describe('Process ID of the backend'),
    }));
    
    // Input schema (allow filtering by user or database later if needed)
    const GetDbConnectionsInputSchema = z.object({});
    type GetDbConnectionsInput = z.infer<typeof GetDbConnectionsInputSchema>;
    
    // Static JSON Schema for MCP capabilities
    const mcpInputSchema = {
        type: 'object',
        properties: {},
        required: [],
    };
  • src/index.ts:16-16 (registration)
    Import statement that brings in the getDatabaseConnectionsTool from its implementation file.
    import { getDatabaseConnectionsTool } from './tools/get_database_connections.js';
  • src/index.ts:105-105 (registration)
    Registration of the tool in the availableTools object, which is later used to populate the MCP server capabilities and handle tool calls.
    [getDatabaseConnectionsTool.name]: getDatabaseConnectionsTool as AppTool,

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It correctly implies a read-only operation ('retrieves'), but does not specify what fields are returned, any authentication requirements, or potential impacts. The description is adequate but lacks detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It front-loads the verb and resource, achieving maximum conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and no annotations, the description provides sufficient context for a simple read tool. However, it could mention the typical fields returned (e.g., user, host, state) to improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters (0 params, 100% schema coverage). The description does not need to explain parameters, and the baseline for 0 params is 4. It adds no parameter info because none are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retrieves' and the resource 'information about active database connections from pg_stat_activity'. It distinguishes from sibling tools like get_database_stats and list_tables by specifying the exact system view used.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like get_database_stats or execute_sql. The description lacks any context for appropriate usage or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.