nexoxa-mcp

Model Context Protocol server for Nexoxa Bridge — full local control by saved connection name (no URLs in MCP).

Security

• Connection URLs are never accepted via MCP tools.
• Names resolve inside Bridge from an encrypted registry synced from the desktop app vault.
• Bridge API is localhost-only (+ optional NEXOXA_MCP_TOKEN).

Tools (36+)

Connection: nexoxa_bridge_list_connections, connect, connect_active, disconnect, status

Database: query, explain, list_schemas, list_tables, table_metadata, table_rows, overview, schema_graph, schema_report, schema_summary, kg_refresh, advisors

SSH: server_dashboard, server_exec, server_kg, analytics_overview

Storage (S3/SFTP/FTP): storage_list, overview, buckets, delete, move, mkdir, download_url

SMTP: smtp_verify, smtp_overview, smtp_send

Fallbacks (offline): nexoxa_schema_report, nexoxa_schema_graph_summary, nexoxa_run_readonly_sql

Setup

1. Save connections in Nexoxa Bridge with names.
2. Launch Nexoxa Bridge Studio (Microsoft Store or desktop install).
3. Add to Cursor:

Production (npm)

{
  "mcpServers": {
    "nexoxa": {
      "command": "npx",
      "args": ["-y", "nexoxa-mcp"]
    }
  }
}

Bridge auto-discovery reads %AppData%\com.nexoxabridge.database-studio\embedded-port.json (default http://127.0.0.1:47821).

Development (monorepo)

{
  "mcpServers": {
    "nexoxa": {
      "command": "node",
      "args": ["D:/Nexoxa_Database/packages/nexoxa-mcp/dist/index.js"],
      "env": {
        "NEXOXA_BRIDGE_URL": "http://127.0.0.1:8080"
      }
    }
  }
}

Use NEXOXA_BRIDGE_URL only when running npm run dev (port 8080). Remove it when testing against the desktop app (port 47821).

Workflow

nexoxa_bridge_list_connections
nexoxa_bridge_connect { "name": "My Postgres" }
nexoxa_bridge_query { "sql": "SELECT 1" }

Or nexoxa_bridge_connect_active if already connected in the UI.

Analytics overview (SSH)

After connecting to an SSH server:

nexoxa_bridge_analytics_overview { "framework": "nuxt", "range": "7d" }

Returns deployment list, pageview/vitals summaries, self-hosted collect paths, and install snippets for @nexoxa/analytics and @nexoxa/speed-insights.

Packages

• nexoxa-bridge-sdk — programmatic Bridge client
• @nexoxa/analytics — web analytics SDK
• @nexoxa/speed-insights — Core Web Vitals SDK
• nexoxa-sdk — Nexoxa cloud API (api.nexoxa.com)

Docs: asteron.nexoxa.com/integrations · Privacy (SDK §8)

MIT