Query and manage databases directly from your IDE
MCP server that runs inside your IDE to connect AI assistants to MySQL, Postgres, SQLite, and MSSQL databases for direct querying and schema inspection.
Maintainer of this project? Claim this page to edit the listing.
1.0.0Add to Favorites
Why it matters
Connect to and interact with multiple database systems (MySQL, Postgres, SQLite, MSSQL) without leaving your development environment, enabling seamless database operations during coding workflows.
Outcomes
What it gets done
Connect to MySQL databases from within your IDE
Query Postgres tables and retrieve results inline
Execute SQL commands against SQLite databases
Manage MSSQL database connections and operations
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-devdb | bash Overview
DevDb MCP Server
DevDb MCP Server is a Model Context Protocol server that runs inside your IDE to connect AI assistants with MySQL, Postgres, SQLite, and MSSQL databases. It enables AI coding tools to query databases, inspect schemas, and access live data directly from your development environment. Use it when you want your AI assistant to have context about your actual database structure and contents while coding, debugging queries, or generating database-aware code. It's ideal for developers who need their AI tools to understand live database schemas and relationships.
What it does
DevDb MCP Server is a Model Context Protocol (MCP) server that runs directly inside your integrated development environment to bridge AI assistants with relational databases. It enables AI coding assistants to connect to MySQL, Postgres, SQLite, and MSSQL databases, allowing them to query data, inspect schemas, and interact with your database infrastructure without leaving your IDE.
When to use - and when NOT to
Use DevDb MCP Server when you need your AI assistant to access live database information during development, such as when writing queries, debugging data issues, understanding schema relationships, or generating database-aware code. It's ideal for developers who want their AI tools to have context about their actual database structure and contents.
Do not use this tool if you're working with databases that contain highly sensitive production data without proper access controls, as it grants your AI assistant direct database access. Avoid using it when you need database interactions to go through a specific API layer or when your security policies prohibit direct database connections from development tools.
Inputs and outputs
You provide database connection credentials (host, port, username, password, database name) for MySQL, Postgres, SQLite, or MSSQL databases. The server runs within your IDE environment and makes these connections available to MCP-compatible AI assistants.
You receive the ability for your AI assistant to execute database queries, retrieve schema information, inspect table structures, and access live data directly through natural language requests to your AI coding assistant.
Integrations
DevDb MCP Server integrates with four major database systems:
- MySQL: Connect to MySQL databases for querying and schema inspection
- Postgres: Access PostgreSQL databases with full query capabilities
- SQLite: Work with local SQLite database files
- MSSQL: Connect to Microsoft SQL Server databases
The server implements the Model Context Protocol (MCP), making it compatible with MCP-enabled AI assistants and IDE extensions.
Who it's for
DevDb MCP Server is built for software developers who use AI coding assistants and work with relational databases. It's particularly valuable for full-stack developers, backend engineers, and data engineers who need their AI tools to understand their database schemas and data structures. Developers working in VS Code or other IDEs with MCP support will benefit from having their AI assistant context-aware of their actual database state, enabling more accurate code suggestions and query generation.
Source README
MCP server that runs directly inside your IDE to connect to MySQL, Postgres, SQLite, and MSSQL databases
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.