gqai-editorial-mcp-server

Remote MCP server exposing read-only access to the editorial (사설) table in the GQAI Supabase project (20250320-exnews-supabase, ~22k Korean newspaper editorials from 35 outlets).

Live deployment

• Endpoint: https://gqai-editorial-mcp.vercel.app/api/mcp

• Hosted on Vercel; every push to main deploys automatically.

Related MCP server: law-search-mcp

Quick install

No auth needed — just point your client at the live endpoint.

Claude Code:

claude mcp add --transport http editorial https://gqai-editorial-mcp.vercel.app/api/mcp

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "editorial": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gqai-editorial-mcp.vercel.app/api/mcp"]
    }
  }
}

Any other Streamable HTTP-capable client: add https://gqai-editorial-mcp.vercel.app/api/mcp as the server URL — see Connecting a client below for the raw config format.

Tools

• search_editorials — keyword + media outlet + date-range search, paginated

• get_editorial — full text of one editorial by id or link

• list_media_outlets — every outlet name and its editorial count

Why it's safe to expose openly

• No auth gate on the MCP endpoint itself — anyone with the URL can call it.

• That's fine here because the editorial table's only RLS policy (editorial_public_select) grants SELECT to anon/authenticated — the app can never write, and it exposes nothing that isn't already readable with the public anon key.

Local development

npm install
cp .env.example .env.local   # fill in SUPABASE_ANON_KEY
npm run dev

The MCP endpoint is http://localhost:3000/api/mcp (Streamable HTTP, JSON-RPC 2.0). Test it with:

curl -X POST http://localhost:3000/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Deploying to Vercel

vercel link
vercel env add SUPABASE_URL
vercel env add SUPABASE_ANON_KEY
vercel deploy --prod

Connecting a client

Any MCP client that supports Streamable HTTP — no auth needed:

{
  "mcpServers": {
    "editorial": {
      "url": "https://gqai-editorial-mcp.vercel.app/api/mcp"
    }
  }
}

For stdio-only clients, bridge with mcp-remote:

{
  "mcpServers": {
    "editorial": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gqai-editorial-mcp.vercel.app/api/mcp"]
    }
  }
}

Notes on the underlying data

• title/content have pg_trgm GIN indexes (editorial_title_trgm_idx, editorial_content_trgm_idx) added specifically to make ILIKE search fast enough to stay under Postgres' statement timeout — without them, search_editorials times out on the ~22k-row table.

• published_at is used as the canonical date for filtering/sorting (falls back to pubdate for display if null, though in practice both are always populated).