KB-5A10
GPT Lookup — Phase 2F-C MCP Production Patch Design — 2026-05-14
2 min read Revision 1
lookupphase-2fmcpproduction-patchagent-data
GPT Lookup — phase-2f-c-mcp-production-patch-design — 2026-05-14
Query
phase-2f-c-mcp-production-patch-design-2026-05-13
Located source
knowledge/current-state/reports/phase-2f-c-mcp-production-patch-design-2026-05-13.md- Title:
Phase 2F-C — MCP Production Patch Design Report (2026-05-13) - Status in source: Investigation + design only. No code changes, no rebuild, no restart, no commit.
Key findings
list_documentslatency is Python-side full-table materialization; recommended patch2F-D1is SQL pushdown plus partialtext_pattern_opsindex.- MCP transport blocker is app-level content negotiation, not nginx; recommended patch
2F-D2ais JSON/SSE response negotiation. move_documentis intentionally deprecated/501 but still advertised; recommended patch2F-D3removes it from MCP schema/dispatcher while preserving HTTP 501 endpoint.- Write latency is dominated by inline vector sync duplicated by the existing PG-NOTIFY listener; recommended patch
2F-D4makes vector indexing async/eventual-consistent. - Public GPT endpoint policy should remain
/gpt-mcp/{token}/mcp -> /mcp-gptwith 8 tools; do not expose/mcp-gpt-fullpublicly.
Recommendation preserved from source
Implement 2F-D1 + 2F-D2a before reconnecting ChatGPT, then 2F-D3, and land 2F-D4 separately after production verification.