From mcp-tools-pro
MCP Database Connector — querying, schema inspection, and data analysis using live database connections. Use when querying or inspecting databases via MCP.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mcp-tools-pro:mcp-db-connectorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
MCP DB Connector is a skill that enables querying, schema inspection, and data analysis by establishing live connections to databases over the MCP protocol. By default, it operates in read-only mode; write operations are only possible when explicitly authorized and enabled. Using connection pool management, multiple concurrent database connections are handled efficiently.
MCP DB Connector is a skill that enables querying, schema inspection, and data analysis by establishing live connections to databases over the MCP protocol. By default, it operates in read-only mode; write operations are only possible when explicitly authorized and enabled. Using connection pool management, multiple concurrent database connections are handled efficiently.
Core principle: READ-ONLY BY DEFAULT — DATA MODIFICATION REQUIRES EXPLICIT AUTHORIZATION.
NO QUERY MAY MODIFY DATA (INSERT/UPDATE/DELETE/DDL) IN A PRODUCTION DATABASE. WRITE PERMISSIONS ARE VALID ONLY WHEN EXPLICITLY AND CONSCIOUSLY ENABLED.
Use this when:
Use this ESPECIALLY when:
Don't skip when:
BEFORE proceeding:
mcp-db-connector connect --type postgresql --host db.example.com --port 5432 --db production --user analyzer --role readonly
mcp-db-connector test --connection-id conn-123
BEFORE proceeding:
mcp-db-connector schema tables --connection-id conn-123
mcp-db-connector schema describe --connection-id conn-123 --table users
mcp-db-connector schema indexes --connection-id conn-123 --table orders
mcp-db-connector schema foreign-keys --connection-id conn-123
BEFORE proceeding:
mcp-db-connector query --connection-id conn-123 --sql "SELECT * FROM users WHERE status = 'active' LIMIT 100"
mcp-db-connector query --connection-id conn-123 --sql "SELECT COUNT(*) FROM orders WHERE created_at > NOW() - INTERVAL '7 days'" --format json
BEFORE proceeding:
mcp-db-connector enable-write --connection-id conn-123 --scope "UPDATE orders SET status WHERE id IN (...) ONLY" --reason "ETL bug fix - approved by #ticket-456"
mcp-db-connector disable-write --connection-id conn-123 # close immediately
Before marking complete:
If you catch yourself thinking:
ALL OF THESE MEAN: STOP. Return to the relevant phase.
Watch for these redirections:
When you see these: STOP. Return to the relevant phase.
| Excuse | Reality |
|---|---|
| "It's just a quick UPDATE, it won't break anything." | Rogue writes bypass validation logic, compromise data integrity, and create audit risks. |
| "LIMIT is unnecessary, the table is small." | Fetching unbounded result sets exhausts memory buffers and introduces network lag. |
| "Testing the connection is a waste of time." | Troubleshooting queries on a bad connection takes far longer than a simple test. |
| "I can write the password in the query string temporarily." | Query logs are saved persistently; plaintext passwords in queries will leak credentials. |
| "I'll close the write permissions later when I'm done." | Leaving write access open invites accidental modifications and introduces security risks. |
After completing this process:
npx claudepluginhub haj1t/senior-dev-squad-skills --plugin mcp-tools-proGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.