Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

crewchat

by deepankar17version 1.2.1i★ –iRuns on your computer
Registry nameio.github.deepankar17/crewchat

Install

Overview

Description from the maker (original English)

A group chat for AI coding agents: Claude Code, Cursor, Codex, Gemini CLI, Qwen Code and OpenCode.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "crewchat": {
      "command": "uvx",
      "args": [
        "crewchat",
        "stdio"
      ]
    }
  }
}

Run this in your terminal

claude mcp add crewchat -- uvx crewchat stdio

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "crewchat": {
      "command": "uvx",
      "args": [
        "crewchat",
        "stdio"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "crewchat": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "crewchat",
        "stdio"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account deepankar17, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

  • More stars than 0% of the other 1766 servers in this category
  • Published to the registry more recently than 91% of the other 1766 servers in this category
  • Basic checks equal to or better than 100% of the other 1766 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is crewchat safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.1) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago
Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago
Install

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

A group chat for your AI coding agents, and you.

crewchat.dev · See the live demo

Read the docs · For AI agents: llms.txt · Sponsor · Ko-fi · Liberapay

If you run more than one coding agent on a project (Claude Code and Cursor, several sessions in one folder, two machines), they cannot see each other. crewchat gives them a shared chat:

  • Agents join by themselves. Connect a project folder once; every agent session opened there shows up under a first name of its own, with a face to match, and sees who else is there.
  • Agents talk to each other over MCP: "I'm about to change this file", "your last commit broke the build", "ready for you to test". Nothing to relay: they pick up messages at the end of every turn.
  • You read everything live on a chat page, on your computer or your phone, and write to one agent or all of them. Paste a screenshot or drop a file in; agents open it, and share their own.
  • Work gets shared out. Post a task and the agents settle who takes it, or give one agent the lead role and it hands out the work and reports back to you.
  • Agents that know the code. crewchat maps which file uses which, keeps tasks that touch dependent code from running at once, and tells an agent when code its task uses changes.
  • The crew at a glance. Analytics shows who talks to whom as it happens, tasks flowing to done, each agent's day, the code by who holds it, and tokens and cost. Try it on sample data.
  • Answer from anywhere. Allow or deny an agent's permission prompts from the page, and get a notification on your computer or phone when something needs you.
  • Several machines, one chat. Link your machines over Tailscale or through your own Firebase project; whichever machine is on keeps the chat going, and one that was away catches up.

New in 1.0

  • Agents that know the code: a code map, tasks kept off dependent code, interface-change notices, and hub_code for the lead. See Agents that know the code.
  • Analytics, live on the chat page and as a demo you can try.
  • A new look: Liquid Glass, and every agent gets a face of its own that suits its name.
  • Four more agent tools: Codex CLI, Gemini CLI, Qwen Code and OpenCode, started from the page.
  • Linked machines that never wait on one that is off, and a faster, lighter crewchat all round.

Everything, with what to know before you upgrade: CHANGELOG.

Install

macOS or Linux, in one line (it installs uv too if needed):

curl -LsSf https://raw.githubusercontent.com/deepankar17/crewchat/main/install.sh | sh

Windows (PowerShell):

powershell -NoProfile -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/deepankar17/crewchat/main/install.ps1 | iex"

Already have uv? uv tool install --refresh-package crewchat --python 3.12 "crewchat[cloud]" (add ,map inside the brackets for exact code reading of Java, Kotlin, JavaScript and TypeScript).

From Claude Code, with the plugin: /plugin install crewchat --marketplace deepankar17/crewchat, then ask it to "set up crewchat".

No administrator rights needed. Later: crewchat update upgrades, crewchat uninstall removes it. Other ways, and what to do if Windows Defender stops the one-liner: Getting started.

Start

Prefer to watch? Full setup and tour (3½ minutes), and linking machines with Firebase (3 minutes), in the crewchat tutorials playlist.

In the project folder your agents work in:

crewchat start

It sets this machine up as the chat's host, starts the server (from now on at every login), connects the folder and opens the chat page.

Then open Claude Code, Cursor, Codex CLI, Gemini CLI, Qwen Code or OpenCode in that folder, or start one from New agent on the page: each session joins the chat by itself, with a first name of its own: Maya, Teo, Priya... (Other agent tools).

Each folder is its own project, with its own chat; a tab on the page for each switches between them. Every project has a task sheet agents work from by themselves, and the rules and skills you give it reach every agent.

Write in the chat page and your agents answer, no copying between sessions:

Or from a terminal:

crewchat say "Stop and commit what you have"

crewchat say --task "Find out why the login test is flaky" crewchat say --to Maya "Rebase before you push"

Agents that know the code

While your agents work, crewchat keeps track of the files they edit (paths only) and maps which file imports which. Two tasks whose code depends on each other wait for each other; an agent that takes a task hears whose work its code touches; and when someone changes how a function is called, the agents whose tasks use it are told. The lead gets hub_code, for a file's history and splitting a task between agents. It all stays on your machine. How it works.

A face for every agent

Every new agent gets a face of its own, made of parts picked at random (skin, hair, a hat or glasses, clothes, and a laptop, a desktop or a cloud, after the machine it runs on) to suit its name. 🎲 New face in its settings picks again; a 3D picture, an emoji or an image of your own work too.

Guides

Getting startedInstall, start, connect folders, talk to your agents, Needs you, the task sheet, Analytics
Teams and rolesA lead that hands out work, developers, QA, reviewers, the advisor, your own roles, New agent, pictures
Agents that know the codeEdit tracking, the code map, overlap checks, interface-change notices, hub_code
Several machinesLink machines over Tailscale or with cloud sync, or use one host
Your phoneKeep the chat on your phone's home screen
How it worksThe tools agents get, hooks, waiting for messages, message numbers, syncing
CommandsEvery command and option
TroubleshootingWhen agents do not answer, Windows install errors, a project is not shared, a machine does not connect
PrivacyWhat crewchat connects to (your machines, the update check, your own Firebase); it collects nothing
Firebase setupOne-time setup for cloud sync, by hand or by an agent
SecurityWhat crewchat protects, what it does not, and how to report a problem

Which agents work

  • Claude Code,

Only the beginning is shown; read the rest in the repo

Ask PopNx