What runtime dependencies does Infra MCP require?
Infra MCP is a Python package installable via `uv` or `pip`. It requires an existing SSH configuration (typically `~/.ssh/config`) and network reachability to target VMs.
@esp4ce
Basic information
Read-only MCP server for on-prem Linux VMs and PostgreSQL over SSH — service health, logs, DB state, and schema exploration without terminal access.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"infra-mcp": {
"command": "infra-mcp",
"args": [
"run"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Infra MCP provides read-only Model Context Protocol access to on-prem Linux VMs and PostgreSQL databases over SSH. It lets agents check service health, retrieve bounded logs, inspect database state, and explore table schemas without direct terminal access, using an allowlist-gated and fully audited remote command layer.
Install with uv tool install infra-mcp or pip install infra-mcp. Generate a starter config from ~/.ssh/config with infra-mcp generate-config, set up read-only PostgreSQL roles with infra-mcp setup, verify reachability with infra-mcp test, and discover services/logs/databases with infra-mcp discover --in-place. Then run with infra-mcp run and register it as a stdio MCP server in your client (e.g., Claude Code, Cursor).
SELECT queries to answer production questionsInfra MCP is a Python package installable via `uv` or `pip`. It requires an existing SSH configuration (typically `~/.ssh/config`) and network reachability to target VMs.
VM access uses SSH keys as configured in the user’s SSH config. Database access runs under a dedicated read‑only PostgreSQL role created by the `infra-mcp setup` command.
All tool outputs are bounded server‑side: log lines (200), DB rows (100), and table/column listings (200). Truncation is always flagged with a `-- TRUNCATED:` marker.
No. Infra MCP is read‑only by design: all database queries run inside a `READ ONLY` transaction using a read‑only PostgreSQL role, and SSH commands are restricted to an explicitly configured allowlist.
Every remote operation is appended to a local JSONL audit log. The audit log can be queried with the `get_audit_log` tool to review recent activity.

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Ask Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

Kaiva Bridge turns your API, database or documents into a managed MCP server for Claude, ChatGPT, Cursor and VS Code. Point it at an OpenAPI or Swagger spec, an API docs link, a cURL command, a Postman collection, a Grap

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
Comments