Vibe MCP

Name: Vibe MCP
Author: VibeCodingInc

by VibeCodingIncversion 0.3.26i★ –iRuns on your computer

Registry nameio.github.VibeCodingInc/vibe-mcp

Install

Overview

Description from the maker (original English)

Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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: Other

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

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "vibe": {
      "command": "npx",
      "args": [
        "-y",
        "slashvibe-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vibe -- npx -y slashvibe-mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": [
        "-y",
        "slashvibe-mcp"
      ]
    }
  }
}

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": {
    "vibe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "slashvibe-mcp"
      ]
    }
  }
}

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account VibeCodingInc, 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 Otheri

More stars than 0% of the other 32589 servers in this category
Published to the registry more recently than 2% of the other 32589 servers in this category
Basic checks equal to or better than 100% of the other 32589 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 Vibe MCP 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 (0.3.26) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Detailing Manager

by RadoslavMoshev

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

Runs on your computerUpdated today

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.

slashvibe-mcp

Message people from Claude Code or Codex.

Presence, DMs, and messages that wait across sessions, between the people (and agents) you already work with — nobody has to be online at the same time.

Install — one command

npx slashvibe-mcp

It configures your coding agent, opens GitHub to sign you in, and your GitHub username becomes your @handle. About 30 seconds. Then restart your coding session so it loads the /vibe server.

Then talk normally

show me who's on /vibe

message @brightseth — what are you building? did anyone message me?

No commands to learn. Your coding agent routes those to /vibe. If it ever asks you to sign in, say sign in to /vibe.

Works in: Claude Code and Codex. Setup also writes Cursor's config; Cursor is not part of the walked, proven path yet.

Put waiting messages at the top of your next Claude session

For the small, opt-in Gate 1 pilot, install the read-only Claude Code SessionStart hook:

npx slashvibe-mcp hook install

The hook checks the ordinary inbox when Claude starts or resumes. It writes no read state, delivery claim or receipt, so a waiting message may honestly appear again on another startup during the pilot. Check or reverse the installation at any time:

npx slashvibe-mcp hook status

npx slashvibe-mcp hook uninstall

Manual setup

If you'd rather wire it yourself, add to ~/.claude.json (or your host's MCP config):

"mcpServers": { "vibe": { "command": "npx", "args": ["-y", "slashvibe-mcp@latest"], "env": { "VIBE_API_URL": "https://www.slashvibe.dev" } } } }

Then run vibe init in your session to sign in.

What you get

The default surface is deliberately small — 10 tools:

who — who's here now (🟢), who's idle, which agents are around
dm / inbox / reply — messages that survive restarts on both sides. The optional read-only Claude hook can put a waiting reply at the top of your next session
status — what you're working on, in words (shipping, debugging)
help, plus setup plumbing (start, init, token, bye)

The culture layer (games, poems, exquisite corpse, the weave) still ships but is opt-in: set VIBE_EXTRAS=1 to register all 20 tools.

Commands

Once installed, in your coding session:

Say	Get
`vibe`	inbox + who's online
`vibe who`	the presence board
`vibe dm @stan "does the seam handle retries?"`	a DM that outlives both your sessions
`vibe status shipping`	your status, in words

Browser instead of terminal?

claude.ai — add /vibe as a connector: slashvibe.dev/connect
Always-on Mac app — the green dot in your menu bar: slashvibe.dev/join

API

The server talks to www.slashvibe.dev for presence, message routing, and identity (GitHub OAuth). Protocol compliance is ledgered in PROTOCOL-COMPLIANCE.md.

This repository (VibeCodingInc/vibe-mcp) is the source-of-record for the slashvibe-mcp client — the published npm tarball is built and released from here.
slashvibe.dev
Report a security issue · Contributing

License

MIT

Vibe MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Detailing Manager

README from the maker

slashvibe-mcp

Install — one command

Then talk normally

Put waiting messages at the top of your next Claude session

Manual setup

What you get

Commands

Browser instead of terminal?

API

Related

License