Vibe Coding Control MCP server

Vibe Coding Control — Remote MCP

Connect your VCC account to read your own projects, tasks and development history, record factual work, and request or retrieve owner decisions.

• Website: https://vibecodingcontrol.com
• Remote MCP: https://vibecodingcontrol.com/mcp
• Support · Privacy · Terms

This repository contains only distribution manifests, connection examples and one workflow skill. The VCC application source and user data are not included. An account is required. Use the normal VCC Google sign-in and OAuth consent; there are no tokens to copy and no server to install. Remote access includes your own current and future VCC projects. Revoke an application at https://vibecodingcontrol.com/mcp/connections.

Connect

Add to Cursor · Add to VS Code

These official install links open the editor confirmation and then the normal OAuth sign-in. If your Markdown viewer blocks editor links, use the steps below. Native editor installation of these links is not yet verified for this release.

codex mcp add vcc-remote --url https://vibecodingcontrol.com/mcp
codex mcp login vcc-remote --oauth-client-registration dcr

claude mcp add --transport http --scope user vcc-remote https://vibecodingcontrol.com/mcp

In Claude Code, open /mcp and complete authentication. Client UI availability depends on the plan, workspace permissions and product version. Merge examples into existing configuration; preserve all other servers and the local vcc entry.

First ask: “Show my VCC projects”, choose a project, then read its context. Reuse existing task/run IDs and one stable idempotency key for each write and retry.

Scope and review

Remote VCC cannot read local files, execute shell commands, verify Git or deploy. Those local workflows require the existing installed VCC Connector. Agents cannot approve owner gates: decisions remain on the VCC website and are bound to the specific run and result. Receiving a decision does not execute the approved action.

plugin.json and mcp.json use Agent Plugins 1.0.0, supported by Cursor and the common OpenAI directory. Both products use the same remote service. There are no embedded credentials, app references or lifecycle hooks. server.json is the official MCP Registry submission descriptor.

Shortened. The full README is on GitHub.