GPT Review — GPT MCP Server Design Phase 1 Rev3 — 2026-05-13

Verdict

APPROVE Phase 2A only — endpoint discovery and prototype scaffolding. Do not deploy public nginx route or connect ChatGPT yet.

Accepted

• Build GPT-specific FastMCP container on VPS.
• Do not touch Claude MCP.
• Use secret path as temporary Phase 1 capability URL.
• ENABLE_WRITE=false default and no write tool advertisement when disabled.
• No deleteDocument in Phase 1.
• Use REST HTTP from gpt-mcp to AgentData, provided endpoints are verified before implementation.

Blocking conditions before public deploy

1. Verify actual AgentData REST endpoints from inside the gpt-mcp container/network before writing the final client. The Rev3 mapping may still be wrong for list/search/create because past surfaces differ between OpenAPI, MCP, and REST.
2. Confirm real AgentData container DNS/port. http://agent-data:8888 is an assumption until tested.
3. Confirm nginx include context. log_format is only valid in http context; if the template is included inside a server block, it will fail. Split http-level log_format and server-level location if needed.
4. Confirm path rewrite for both /mcp and /mcp/ using live tests before giving the URL to ChatGPT.
5. Ensure public non-matching /gpt-mcp/* does not leak any real secret through default logs. Do not print secret URLs.
6. docker exec gpt-mcp curl requires curl in the image; otherwise use a Python/httpx test script or install curl intentionally.

Phase 2 allowed scope

• Create files under /opt/incomex/gpt-mcp/.
• Build container locally on VPS.
• Join correct Docker network.
• Run internal endpoint discovery tests.
• Run FastMCP locally/internal only.
• Produce report with redacted outputs.

Phase 2 not allowed yet

• No public nginx deploy until endpoint discovery passes.
• No ChatGPT connector connection yet.
• No ENABLE_WRITE=true yet.
• No secret in chat/report/AgentData.

Required Phase 2A report

Print directly in chat:

• Docker network and resolved AgentData host/port.
• curl/httpx results for health, kb/list, chat, documents get, batch, create/update/patch schema probe if safe.
• Final confirmed mapping table.
• FastMCP tools/list from internal MCP client.
• Nginx config placement plan: http context vs server context.
• Decision whether Phase 2B public route can proceed.