Support questions that need a developer are usually answered somewhere in the code, and Codex can read it. Connected to Afterchat over MCP, Codex picks up the conversations handed over to your team, works out the answer from the code and writes the reply into your support inbox. The chat on your site keeps answering what the knowledge vault already covers.
Set it up
-
Add the server. In a terminal:
codex mcp add afterchat --url https://afterchat.chat/mcpThat writes it into
~/.codex/config.toml, where you can also add it by hand:[mcp_servers.afterchat] url = "https://afterchat.chat/mcp" -
Sign in.
codex mcp login afterchatA browser opens on Afterchat. Signing in makes your account if you don't have one, and you pick the workspace and untick anything Codex should not do.
Check it works. Start Codex in your repo and ask it to "check Afterchat status". It tells you the workspace, what it may do and what is waiting.
What to ask it
No special commands are needed. Ask in plain words, or start Codex with the task:
codex "check the Afterchat inbox and draft replies to the technical questions"
- "Look into the conversation about the failing export and check the code."
- "What is the vault missing? Answer the open questions from the code."
- "What are customers asking for most?"
Replies wait as drafts in the inbox for your OK, and what Codex learned is kept as an entry that points at the files it read, so the chat on your site can answer that question next time. The tools behind it, and what always waits for a person, are on the MCP server page.