Answer support chats from Codex

One command adds Afterchat to Codex. It reads the chats waiting on you, checks your code and drafts the replies, and every answer is kept for the chat on your site.

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

  1. Add the server. In a terminal:

    codex mcp add afterchat --url https://afterchat.chat/mcp

    That writes it into ~/.codex/config.toml, where you can also add it by hand:

    [mcp_servers.afterchat]
    url = "https://afterchat.chat/mcp"
  2. Sign in.

    codex mcp login afterchat

    A 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.

  3. 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.

Questions

Does Codex support MCP servers with OAuth?

Yes. codex mcp add registers a remote server by its address, and codex mcp login signs in to it in the browser, which is how Afterchat connects. There is no API key to paste.

Can Codex reply to customers without me?

It drafts the replies. By default each one waits in the Afterchat inbox until someone approves it, and hold rules keep prices, refunds and legal terms with a person whatever the setting.

Does Afterchat see our code?

No. Codex reads your code with the access it already has and sends back only the replies, notes and entries it writes.

Does Codex have to stay open?

No. The chat on your site answers around the clock from the knowledge vault and hands over what it can't answer. Codex works through those when you ask it to.

What does it cost?

Afterchat is free while in early access, within a monthly AI allowance that covers a small team's chats. Codex is billed by OpenAI as usual.

Works with

MCP server MCP server for customer support Connect Claude Code, Cursor or Codex to your support inbox over MCP. Answer chats from your code, keep every answer, approve what reaches customers. Claude Code Claude Code for customer support Use Claude Code for customer support: one command connects it to your inbox over MCP, it answers from your code, and every answer is kept. Claude Claude for customer support How to use Claude for customer support: add Afterchat from Claude's connector directory, and Claude works your support inbox, drafts replies and keeps your knowledge vault. Cursor Customer support in Cursor over MCP Connect Cursor to your support inbox over MCP in one click. Cursor's agent answers support chats from your code, and every answer is kept for the chat on your site.

Read next

Knowledge base An AI support chatbot trained on your docs and your code How to give an AI support chatbot your own knowledge: why crawling your docs is only the start, how short checked entries built from your docs, code and chats answer better, and how to keep them true. Buyer's guide AI customer support for SaaS: a checklist for small teams What to look for in an AI support chat when your team is small and answers its own customers: sourced answers, honest handovers, learning from every chat, knowing what to build, and working with your coding agent. Feature requests How to track feature requests from support chats Support chats are where customers say what they wish your product did. How to capture those requests, group different wordings into one, rank them by how many accounts asked, and tell everyone when it ships.