VibeCoding MCP Server

If you already use VibeCoding MCP, the vibecoding mcp mcp server is the piece that lets your assistant work with it directly. Conversation-driven development framework for rapid MVP/POC creation.

What the server does

2. 添加 VibeCoding MCP 設定： json { "mcpServers": { "vibecoding-context-manager": { "command": "node", "args": ["/path/to/your/vibeCoding-template/dist/vibe-services/context-manager/index.js"], "description": "VibeCoding 上下文管理服務" } }, "vibecoding.enabled": true, "vibecoding.defaultProvider": "cursor" }

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Credentials and setup notes

Configuration is passed through the environment: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by Zenobia000; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.