Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/cuongtl1992/mcp-dbs/project-overviewgit clone --depth 1 https://github.com/cuongtl1992/mcp-dbsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/cuongtl1992/mcp-dbs/project-overview)<a href="https://agentmods.dev/rules/cuongtl1992/mcp-dbs/project-overview"><img src="https://agentmods.dev/badge/rules/cuongtl1992/mcp-dbs/project-overview.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00474 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
project-overview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
MCP Database Server Project Overview
Project Purpose
This project provides an MCP (Model Context Protocol) server implementation for database connections. It allows LLM-powered applications to connect to and query databases through the MCP protocol.
Key Technologies
- TypeScript
- Node.js
- Model Context Protocol (MCP)
- Database Connections (SQLite, PostgreSQL, SQL Server)
- ESM Modules
Architecture
The project follows a modular architecture:
Core Components
- Database Interfaces: Defines the common interface that all database implementations must follow.
- Database Implementations: Concrete implementations for each supported database type.
- MCP Server: The main server that handles MCP protocol communication.
- Factory: Creates database instances based on configuration.
- Tools: MCP tool implementations for database operations.
- Resources: MCP resource implementations for database schema information.
Directory Structure
-
src/: Source codeinterfaces/: TypeScript interfaces for the codebasedatabases/: Database implementationstools/: MCP tool implementationsresources/: MCP resource implementationsserver.ts: Main MCP server implementationfactory.ts: Database factoryindex.ts: Entry point and exports
-
test/: Test files -
dist/: Compiled JavaScript output -
assets/: Static assets
Important Development Notes
- The project uses ES modules (ESM) with
.jsextensions in import paths. - Some dependencies (like 'pg') are CommonJS modules and require special import handling.
- All database implementations follow the same interface for consistency.
- The server supports both STDIO and SSE transports for different use cases.
Common Tasks
- Adding a new database type: Create a new implementation in
src/databases/following the Database interface, then update the factory. - Adding new MCP tools: Add to the tools directory and register in the server.
- Running in development: Use
npm run devto start the TypeScript compiler in watch mode. - Testing: Run
npm testto execute the Jest test suite.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 57 lines · 0 tokens per session scan A f687b0d2e424
project-overview is a cursor rule published in the GitHub repository cuongtl1992/mcp-dbs (21 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 474 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
sqlmodel
Satisfying the type checker when working with SQLModel.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.