Schema | pg_mcp_qauth

pg_mcp_qauth

Describes the environment variables required to run the server.

Name	Required	Description	Default
`PG_HOST`	Yes	PostgreSQL host.
`PG_PORT`	Yes	PostgreSQL port.
`PG_USER`	Yes	PostgreSQL user (must have SET ROLE privileges).
`JWKS_URI`	Yes	The JWKS endpoint URL for verifying token signatures.
`MAX_ROWS`	No	Maximum number of rows returned (auto-LIMIT).
`ALGORITHMS`	Yes	The asymmetric signing algorithm(s) allowed (e.g., RS256, ES256, PS256, EdDSA).
`AUTH_ISSUER`	Yes	The issuer URL of the Authorization Server.
`PG_DATABASE`	Yes	PostgreSQL database name.
`PG_PASSWORD`	Yes	PostgreSQL password.
`ROLES_CLAIM`	Yes	The flat JWT claim containing group/role names.
`DEFAULT_ROLE`	Yes	The default PostgreSQL role to set when no group matches.
`MCP_BASE_URL`	No	Externally reachable URL for RFC 9728 resource metadata (set when behind a reverse proxy).
`ROLE_MAP_JSON`	Yes	JSON mapping group names to PostgreSQL roles.
`RLS_USER_CLAIM`	Yes	The JWT claim used for row-level security (e.g., email).
`REQUIRED_AUDIENCE`	Yes	The required audience for access tokens (mandatory).
`ALLOW_SYSTEM_SCHEMAS`	No	Whether to allow access to system schemas (e.g., 'true'/'false').	false
`STATEMENT_TIMEOUT_MS`	No	Statement timeout in milliseconds.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues