CoChat MCP – Let your team review what your coding agent is building
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
What it does
In the maker’s words, at launch
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models review it, and you pull all the feedback back into your agent's context with one command. Decisions can be saved as project memories that persist across sessions and are searchable by anyone. What it does: Plans: Auto-shared as collaborative threads. Pull feedback back into your terminal. Cross-model review: Have GPT review your Claude plan, or vice versa. Project memories: Semantic memory that persists across sessions, models, and people. Ask: Query your project's knowledge base from the terminal. Auto-scoping: Detects your project from git remote. No config needed. Setup is one command per agent. Auto-share behavior is configurable (off/plan/all). MIT licensed, available on npm: npx @cochatai/mcp-cochat Happy to answer questions about the architecture or the MCP protocol integration.
Does the same job
all alternatives →
MCP-Builder.ai11d ago · mcp-builder.ai · ▲174The fastest way to connect your data with your AI Tools.
ElevenLabs MCP in Claude19d ago · claude.ai · ▲155Create and manage ElevenLabs voice agents in your chat
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 27d ago · cactuscompute.com
