chat-mcp
# chat-mcp
A local Codex plugin for code reviews and analysis through your ChatGPT account in Chrome.
## 1. Install
Requires **Codex, Node.js 22+, Git, Chrome 116+**, and a ChatGPT account.
```sh
git clone https://github.com/phykn/chat-mcp.git
cd chat-mcp
npm run setup
```
Setup registers the local Codex plugin with its MCP tools and usage skill, and prepares the Chrome extension.
## 2. Connect Chrome
1. Open `chrome://extensions` and turn on **Developer mode**.
2. Click **Load unpacked** and select the extension folder printed by setup.
3. ChatGPT opens and connects automatically. Sign in and select **Chat** if shown.
Keep the connected tab open. It reconnects after Chrome restarts.
While waiting for a response, Chat MCP selects this tab so ChatGPT can finish rendering.
Keep Chrome visible and the PC awake while requests run. After a screen lock or sleep, restore the screen and retry the same request to retrieve its answer.
## 3. Use it
Start a new Codex task and say:
> Use Chat MCP to review my changes.
Codex can also invoke it automatically during development tasks.
## Update
Run `git pull` and `npm run setup` in the project folder, then start a new Codex task. The connected extension updates automatically.
## Usage notice
For individual development workflows, not bulk collection or multi-user service hosting. This project is not affiliated with OpenAI.
Browser automation may conflict with service terms and lead to account restrictions or suspension. You are responsible for complying with applicable [terms and policies](https://openai.com/policies/), including for personal use.
Selected code, diffs, and prompts are sent to ChatGPT. Only share content you are authorized to disclose; exclude credentials and confidential information.
## License
[MIT](LICENSE). Provided without warranty; see the license for limitations of liability.
TDQS
Scored across 4 tools
The tools are mostly distinct: health checks, cancelations, general questions, and code reviews each have clear roles. There is mild overlap between chatgpt_ask and review_with_chatgpt for code-related inquiries, but their descriptions give enough separation.
Naming is readable and consistently lowercase snake_case, but the pattern is mixed: chatgpt_ask, chatgpt_health, and chatgpt_cancel use a chatgpt_ prefix, while review_with_chatgpt places the verb first and the service as a suffix. This is a minor but noticeable inconsistency.
Four tools are well-scoped for a ChatGPT integration: ask, review, health, and cancel cover the core workflow without redundancy or bloat. The count feels appropriate for the server's purpose.
The set covers the essential interaction lifecycle: health check, general ask, code review, and cancellation. Minor gaps exist, such as no explicit session/history inspection tool, but agents can likely accomplish their main goals with these tools.