Skip to content
PerSQL PerSQL PerSQL

Other MCP clients

If your MCP client only speaks stdio (Continue, the OpenAI Codex CLI, older Cline builds, custom OpenAI Agents SDK runners), bridge to PerSQL through the mcp-remote proxy. Recent mcp-remote builds handle the OAuth handshake automatically when no header is provided; older builds need a static bearer token.

OAuth — current mcp-remote:

{
  "mcpServers": {
    "persql": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.persql.com"]
    }
  }
}

Bearer fallback — older mcp-remote or runtimes without OAuth delegation:

{
  "mcpServers": {
    "persql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.persql.com",
        "--header",
        "Authorization: Bearer psql_live_…"
      ]
    }
  }
}

The exact path to drop this in depends on the client:

  • Continue.dev — ~/.continue/config.json under mcpServers.
  • OpenAI Codex CLI — ~/.codex/config.toml, the equivalent [mcp_servers.persql] block with command and args keys.
  • Custom runners — wherever the client reads MCP server config.

mcp-remote is maintained by the MCP community; install on demand via npx, no global install needed.

What you get

Section titled “What you get”

Same set of about sixty SQL-shaped tools as every other install path. See the MCP reference for the catalog.