PostgreSQL API SSH MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENCRYPTION_KEY | No | Override encryption key for coordinated environments (default: auto-generated .mcp_profiles.key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_psql_managerC | 🐘 PostgreSQL Manager - безопасные операции с базой данных: setup_profile, list_profiles, quick_query, show_tables, describe_table, sample_data, insert_data, update_data, delete_data, database_info. Шифрование AES-256-CBC, защита от SQL injection, валидация входных данных. |
| mcp_ssh_managerB | 🔐 SSH Manager - безопасные SSH операции: setup_profile, list_profiles, execute, system_info, check_host. Защита от command injection, санитизация команд, ограничения безопасности. |
| mcp_api_clientB | 🌐 API Client - безопасные HTTP запросы: get, post, put, delete, patch, check_api. Валидация URL, санитизация заголовков, защита от SSRF, ограничения размера данных. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: mcp_api_client handles HTTP API requests, mcp_psql_manager manages PostgreSQL database operations, and mcp_ssh_manager performs SSH operations. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.
All tool names follow a consistent pattern with the prefix 'mcp_' followed by a descriptive suffix (api_client, psql_manager, ssh_manager). This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the server feels thin for its broad purpose of handling PostgreSQL, API, and SSH operations. While each tool bundles related functions, the low count may limit granular control and could be expanded to better cover the domain's scope.
The tools provide comprehensive coverage for their respective domains: API client supports common HTTP methods, PostgreSQL manager includes essential CRUD operations and database management, and SSH manager covers key remote execution tasks. Minor gaps might exist, such as advanced API features or SSH file transfers, but core workflows are well-covered.