db-oauth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | The log level for the server (e.g., debug, info, error) | info |
| OAUTH_API_BASE_URL | Yes | The base URL for the OAuth API | |
| OAUTH_AUTHORIZE_URL | Yes | The OAuth authorization URL for the MCP server |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connection_statusA | Show whether you're connected and, for each available database connection, which user and engine it uses and when it expires. |
| disconnectA | Disconnect from all database connections. Revokes the current access token and clears cached credentials. The next tool call will require re-authentication. |
| list_connectionsA | List the database connections available in the current session. Returns the name (pass to |
| list_schemaA | List tables or describe a specific table's columns for a given connection. Pass |
| query_databaseA | Execute a read-only SQL query against one of the configured database connections. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: showing connection status, disconnecting, listing connections, exploring schema, and querying data. No overlap in functionality.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_connections, query_database), including the standalone verb 'disconnect' which is standard for such actions.
With 5 tools, the server covers essential operations for a read-only database interface without being overly numerous or sparse. The count fits the scope perfectly.
The tools provide full lifecycle coverage for a read-only database MCP: status, listing connections, schema exploration, querying, and disconnection. No obvious missing features.