English Français العربية

Vibe Coding Control

Official registry Developer tools

Your VCC projects, tasks, AI development history and owner decisions. Sign in with your VCC account.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http vibe-coding-control 'https://vibecodingcontrol.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vibe-coding-control": {
            "type": "http",
            "url": "https://vibecodingcontrol.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

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.

Languages: English and Russian. The workflow answers in the user's language; tool names and arguments are the same. Русский: подключение по адресу https://vibecodingcontrol.com/mcp, вход в аккаунт VCC и ответы на языке пользователя.

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 normal VCC sign-in (Google or email/password) 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.

PlatformSupported connection
VS CodeMCP: Add Server → HTTP → enter the MCP URL → sign in. See connections/vscode.json for the equivalent configuration.
CursorAdd the URL under MCP settings and complete OAuth, or install this Agent Plugins package when the public marketplace listing is approved.
ClaudeInstall from the Claude directory (published Community connector), or Settings → Connectors → Add custom connector → enter the MCP URL → Connect and sign in.
ChatGPTThe official VCC app is under OpenAI review. ChatGPT Business and Enterprise/Edu workspace admins can add VCC now: Plugins → + → Add custom MCP server → MCP URL → OAuth/DCR.
CodexUse the same OpenAI plugin when published, or the commands below for the CLI.
Windsurf / Devin DesktopCascade: add the entry in connections/cascade.json to the existing MCP config, then complete OAuth. Devin Local: devin mcp add -s user vcc-remote https://vibecodingcontrol.com/mcp, then devin mcp login vcc-remote. Cascade has no MCP marketplace or one-click install.
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.

Review scenarios and recording guide. Distribution package 0.1.2 includes the approved VCC logo and icon. The official MCP Registry entry is published, and so is the Claude directory listing; other platform directory reviews remain separate. No marketplace approval is implied by this repository or a ZIP download. The OpenAI submission is under review.

Frequently asked questions

What is Vibe Coding Control?

Your VCC projects, tasks, AI development history and owner decisions. Sign in with your VCC account.

How do I install Vibe Coding Control?

It runs as a remote server. In Claude Code: claude mcp add --transport http vibe-coding-control 'https://vibecodingcontrol.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Vibe Coding Control need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Vibe Coding Control open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Vibe Coding Control?

It is published by OMNOM-111. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.