Connect your AI agent to every database in PromptQuery

Claude Code

Auto-registered to ~/.claude.json. To wire it manually:

json · ~/.claude.json
{
  "mcpServers": {
    "promptquery": {
      "type": "sse",
      "url": "http://localhost:7549/sse",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Cursor

Auto-registered to ~/.cursor/mcp.json.

json · ~/.cursor/mcp.json
{
  "mcpServers": {
    "promptquery": {
      "url": "http://localhost:7549/sse",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Windsurf

Auto-registered to ~/.codeium/windsurf/mcp_config.json.

json · ~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "promptquery": {
      "serverType": "sse",
      "url": "http://localhost:7549/sse",
      "apiKey": "<your-token>"
    }
  }
}

Codex

OpenAI Codex CLI uses TOML at ~/.codex/config.toml. PromptQuery writes a stdio↔SSE bridge entry so it works on every Codex version:

toml · ~/.codex/config.toml
[mcp_servers.promptquery]
command = "npx"
args = ["-y", "mcp-remote", "http://localhost:7549/sse", "--header", "Authorization: Bearer <your-token>"]

GitHub Copilot

Copilot Chat in VS Code reads MCP servers from the User mcp.json:

• macOS ~/Library/Application Support/Code/User/mcp.json
• Linux ~/.config/Code/User/mcp.json
• Windows %APPDATA%\Code\User\mcp.json

json · mcp.json
{
  "servers": {
    "promptquery": {
      "type": "sse",
      "url": "http://localhost:7549/sse",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Antigravity

Auto-registered to ~/.antigravity/mcp.json.

json · ~/.antigravity/mcp.json
{
  "mcpServers": {
    "promptquery": {
      "type": "sse",
      "url": "http://localhost:7549/sse",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

OpenCode

Auto-registered to ~/.config/opencode/opencode.json.

json · opencode.json
{
  "mcp": {
    "promptquery": {
      "type": "remote",
      "url": "http://localhost:7549/sse",
      "enabled": true,
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Credential Security

Database credentials shared across a team are encrypted at rest using Supabase Vault — a server-side encryption layer powered by pgsodium. Host addresses, usernames, passwords, and SSH keys never appear in plaintext in the database.

Personal connections (not shared with a team) are encrypted client-side using AES-256-GCM with a key derived from your user identity — they never leave your device unencrypted.

AI Query Permissions

When an AI agent attempts to run a write query via MCP, PromptQuery intercepts the request and shows the AI Query Permissions dialog. You can grant or deny each operation type individually:

• INSERT — add new rows to tables
• UPDATE — modify existing rows
• DELETE — remove rows from tables
• DDL — schema and admin operations (CREATE, DROP, ALTER, BACKUP, RESTORE)

You can choose to grant permission just this time or always for that connection. Persistent permissions are saved locally and can be changed at any time by right-clicking the connection in the sidebar and selecting AI Query Permissions.

Connection Permissions

For team accounts, PromptQuery enforces a separate layer of connection-level permissions that control what each team member can do on shared connections:

• Connect — connection is visible in the sidebar; required for all other permissions
• Select — run SELECT queries
• Update — run UPDATE queries
• Insert — run INSERT queries
• Delete — run DELETE queries
• DDL — CREATE, DROP, ALTER, TRUNCATE — schema changes

If the Connect permission is revoked, all other permissions are automatically disabled and the member cannot access the connection at all. Permissions are checked on every query execution — the team owner is never restricted.