Database Bridge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 3000 |
| DB_SSL | No | Enable SSL/TLS | |
| DB_HOST | No | Database host | 127.0.0.1 |
| DB_NAME | No | Database name (leave empty for multi-DB mode) | |
| DB_PASS | No | Database password | |
| DB_PORT | No | Database port | 3306 |
| DB_TYPE | No | Database type | mysql |
| DB_USER | No | Database user | root |
| MYSQL_DB | No | MySQL database name (backward compatibility) | |
| DB_SSL_CA | No | CA certificate path | |
| SQLITE_DB | No | SQLite database path (:memory: for in-memory) | |
| DB_SSL_KEY | No | Client key path | |
| MYSQL_HOST | No | MySQL host (backward compatibility) | 127.0.0.1 |
| MYSQL_PASS | No | MySQL password (backward compatibility) | |
| MYSQL_PORT | No | MySQL port (backward compatibility) | 3306 |
| MYSQL_USER | No | MySQL user (backward compatibility) | root |
| DB_SSL_CERT | No | Client certificate path | |
| IS_REMOTE_MCP | No | Enable HTTP mode | |
| POSTGRESQL_DB | No | PostgreSQL database name | |
| POSTGRESQL_HOST | No | PostgreSQL host | 127.0.0.1 |
| POSTGRESQL_PORT | No | PostgreSQL port | 5432 |
| DB_READ_ONLY_MODE | No | Global read-only mode | false |
| MYSQL_SOCKET_PATH | No | Unix socket path (priority over host/port) | |
| REMOTE_SECRET_KEY | No | Authentication token for HTTP mode | |
| ALLOW_DDL_OPERATION | No | Global DDL permission | false |
| DB_CONNECTION_LIMIT | No | Connection pool size | 10 |
| MULTI_DB_WRITE_MODE | No | Allow writes in multi-DB mode | false |
| ALLOW_DELETE_OPERATION | No | Global DELETE permission | false |
| ALLOW_INSERT_OPERATION | No | Global INSERT permission | false |
| ALLOW_UPDATE_OPERATION | No | Global UPDATE permission | false |
| SCHEMA_DDL_PERMISSIONS | No | Schema-specific DDL permissions (format: schema1:true,schema2:false) | |
| SCHEMA_DELETE_PERMISSIONS | No | Schema-specific DELETE permissions (format: schema1:true,schema2:false) | |
| SCHEMA_INSERT_PERMISSIONS | No | Schema-specific INSERT permissions (format: schema1:true,schema2:false) | |
| SCHEMA_UPDATE_PERMISSIONS | No | Schema-specific UPDATE permissions (format: schema1:true,schema2:false) | |
| DB_SSL_REJECT_UNAUTHORIZED | No | Strict SSL validation | |
| MYSQL_DISABLE_READ_ONLY_TRANSACTIONS | No | Disable read-only transactions for MySQL (not recommended) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LucasSiqueiraSurreco/mcp-db-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server