io.github.Optisol-Business/db-metadata-extractor-mcp
Enables extraction and querying of database schema metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle databases, saving results locally for analysis.
README
mcp-name: io.github.Optisol-Business/db-metadata-extractor-mcp
Database Metadata Extractor MCP Server
A Model Context Protocol (MCP) server that extracts and queries database schema metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle databases.
Features
- ✅ Multi-database support: PostgreSQL, Snowflake, SQL Server (MSSQL), BigQuery, Oracle
- ✅ Complete schema extraction: Tables, columns, primary keys, indexes, constraints
- ✅ Local JSON output: Saves metadata directly to local folder (no cloud required)
- ✅ Query interface: Search and filter metadata by table/column names
- ✅ Pagination support: Browse large schemas efficiently
- ✅ VS Code integration: Works with VS Code Agent Mode
- ✅ CLI customizable: Transport options (stdio, HTTP)
Installation
From PyPI
pip install db-metadata-extractor-mcp
From Source
git clone https://github.com/Optisol-Business/db-metadata-extractor-mcp.git
cd db-metadata-extractor-mcp
pip install -e .
Quick Start
1. Start the MCP Server
db-metadata-extractor-mcp
The server starts in stdio mode by default and listens for MCP client connections.
2. Configure in Claude Desktop
Add to ~/.config/Claude/claude_desktop_config.json (macOS/Linux) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"db-metadata-extractor": {
"command": "db-metadata-extractor-mcp",
"args": [],
"env": {}
}
}
}
Restart Claude Desktop.
3. Use in Claude
Tell Claude:
Extract metadata from my PostgreSQL database and save it to
/tmp/output
Claude will use the server's tools to extract and query your database schema.
Tools
extract_metadata
Extracts complete schema metadata from a database.
Parameters:
db_type(required):postgresql,snowflake,sqlserver,bigquery,oracleoutput_path(required): Local directory for JSON outputdatabase_name: Database/schema namehost: Database host (not needed for BigQuery/Snowflake)port: Database portusername: Database userpassword: Database passwordschema_name: Specific schema (optional)tables: Array of table names to extract (optional)account: Snowflake account IDwarehouse: Snowflake warehouserole_name: Snowflake roleproject_id: BigQuery project IDservice_account_key: BigQuery service account JSON (base64 encoded)
Returns:
- File path where metadata was saved
- Summary statistics (table count, column count, etc.)
query_metadata
Query previously extracted metadata.
Parameters:
filepath(required): Path to metadata JSON filetable_name: Filter by table name (substring match)field_name: Filter by column name (substring match)page: Page number (default: 1)page_size: Results per page (default: 20)
Returns:
- Paginated table results matching filters
Examples
PostgreSQL
# Via Claude
"Extract all tables from my dev PostgreSQL database at localhost:5432"
Parameters Claude will use:
{
"db_type": "postgresql",
"host": "localhost",
"port": 5432,
"database_name": "dev_db",
"username": "postgres",
"password": "your_password",
"output_path": "/tmp/db_metadata"
}
Snowflake
"Extract schema from Snowflake account XYZ123"
Parameters:
{
"db_type": "snowflake",
"account": "XYZ123",
"username": "your_user",
"password": "your_password",
"warehouse": "COMPUTE_WH",
"role_name": "ANALYST",
"database_name": "PRODUCTION",
"output_path": "C:/metadata"
}
BigQuery
"Extract metadata from BigQuery project my-project-123"
Parameters:
{
"db_type": "bigquery",
"project_id": "my-project-123",
"service_account_key": "base64_encoded_json_key",
"output_path": "/tmp/bq_metadata"
}
Advanced Usage
Custom Transport
Start with HTTP transport:
db-metadata-extractor-mcp --transport streamable-http --port 3000
Environment Variables
# Set database credentials via env
export DB_HOST=localhost
export DB_USER=postgres
export DB_PASSWORD=secret
db-metadata-extractor-mcp
Output Format
The extracted metadata is saved as a JSON file with structure:
{
"source": {
"db_type": "postgresql",
"extracted_at": "2026-04-09T14:30:00",
"host": "localhost"
},
"schemas": [
{
"schema_name": "public",
"tables": [
{
"table_name": "users",
"columns": [
{
"column_name": "id",
"data_type": "int",
"is_nullable": false,
"is_primary_key": true
},
{
"column_name": "email",
"data_type": "varchar",
"is_nullable": false
}
],
"indexes": [
{
"index_name": "users_email_idx",
"columns": ["email"]
}
]
}
]
}
]
}
Requirements
- Python 3.8+
- For PostgreSQL:
psycopg2-binary - For Snowflake:
snowflake-connector-python - For SQL Server:
pyodbc,pymssql - For BigQuery:
google-cloud-bigquery - For Oracle:
oracledb
Troubleshooting
Connection Errors
Problem: "Unable to connect to database"
Solution: Verify credentials and network access:
# Test PostgreSQL connection
psql -h localhost -U postgres -c "SELECT 1"
# Test Snowflake
snowsql -a XYZ123 -u your_user
Permission Errors
Problem: "Access denied" or "insufficient permissions"
Solution: Ensure database user has:
SELECTon tablesUSAGEon schemasCONNECTon databases
Large Schema Timeouts
Problem: Extraction times out on large databases
Solution: Extract specific schema/tables:
{
"schema_name": "public",
"tables": ["users", "orders"] // Specify subset
}
License
MIT License - See LICENSE file
Contributing
Contributions welcome! Please:
- Fork the repository
- Create feature branch
- Submit pull request
Support
- GitHub Issues: https://github.com/Optisol-Business/db-metadata-extractor-mcp/issues
- Documentation: See MCP_REGISTRY_GUIDE.md
Links
- PyPI: https://pypi.org/project/db-metadata-extractor-mcp/
- GitHub: https://github.com/Optisol-Business/db-metadata-extractor-mcp
- MCP Spec: https://modelcontextprotocol.io/
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.