Evan
c25a321e88
* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
29 lines
904 B
TOML
29 lines
904 B
TOML
id = "postgresql"
|
|
name = "PostgreSQL"
|
|
description = "Query and manage PostgreSQL databases through the MCP server"
|
|
category = "data"
|
|
icon = "🐘"
|
|
tags = ["database", "sql", "relational", "postgres", "queries"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@modelcontextprotocol/server-postgres@0.6.2"]
|
|
|
|
[[required_env]]
|
|
name = "POSTGRES_CONNECTION_STRING"
|
|
label = "PostgreSQL Connection String"
|
|
help = "A full connection URI (e.g., postgresql://user:password@host:5432/dbname)"
|
|
is_secret = true
|
|
get_url = ""
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Obtain your PostgreSQL connection string in the format: postgresql://user:password@host:5432/dbname.
|
|
2. Ensure the database user has the necessary read/write permissions for the tables you want to access.
|
|
3. Paste the full connection string into the POSTGRES_CONNECTION_STRING field above.
|
|
"""
|