The questions that reach a developer are usually about how the product behaves, and Cursor already has the code open. With Afterchat connected over MCP, Cursor's agent can read the conversation, find the answer in the code and write the reply into your support inbox, while the chat on your site keeps answering everything the knowledge vault covers.
Set it up
-
Add the server. One click opens Cursor with it filled in:
Or add it by hand to
~/.cursor/mcp.json, under"mcpServers":"afterchat": { "url": "https://afterchat.chat/mcp" } Sign in. Open Cursor Settings, find afterchat in the MCP list and choose Connect. A browser opens on Afterchat. Signing in makes your account if you don't have one, and you pick the workspace and untick anything the agent should not do.
Check it works. In a chat in Agent mode, ask "check Afterchat status". It tells you the workspace, what it may do and what is waiting.
Share it with your team
To give everyone working in the repo the same setup, put the server in the project's own .cursor/mcp.json instead:
{
"mcpServers": {
"afterchat": { "url": "https://afterchat.chat/mcp" }
}
}
Nothing secret goes in the file, since there is no API key. Each person still signs in as themselves, so every agent works as the person who connected it, with that person's role, and your workspace's rules apply to all of them.
What to ask it
No special commands are needed. In Agent mode, ask in plain words:
- "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 the agent 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.