Vibe Coding Control

io.github.OMNOM-111Published by GitHub account OMNOM-111v0.1.2Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Remote MCP that connects an assistant to a VCC account to read projects, tasks and AI development history, record work, and handle owner decisions.

What you can do
  • Read the user's VCC projects, tasks and AI development history
  • Record factual work against existing tasks and runs
  • Request or retrieve owner decisions tied to a specific run and result
  • Answer in the user's language (English or Russian) with the same tool names and arguments
When to use it
Useful when you work inside Vibe Coding Control and want an assistant in VS Code, Cursor, Claude, Codex or similar to see your project context, log work, and pull owner decisions without switching to the website.
Requirements
A remote endpoint at vibecodingcontrol.com/mcp; no install or tokens to copy. A VCC account with normal sign-in (Google or email/password) and OAuth consent. Client support for HTTP transport and OAuth; some clients need manual URL entry or CLI commands.
Before you install
Access covers your own current and future VCC projects, so review the OAuth consent scope. Writes record work in your account; reuse stable idempotency keys to avoid duplicates. Agents cannot approve owner gates, and receiving a decision does not execute the approved action. It cannot read local files, run shell commands, verify Git or deploy. Revoke access from the connections page when done.

Installation

In SourceWeft

  1. Open Vibe Coding Control in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OMNOM-111%2Fvcc-remote/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vibe-coding-control": {
      "type": "http",
      "url": "https://vibecodingcontrol.com/mcp"
    }
  }
}

README

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.
sh
codex mcp add vcc-remote --url https://vibecodingcontrol.com/mcpcodex mcp login vcc-remote --oauth-client-registration dcr
sh
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.

Source: README.md at commit b30e99e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.2LatestOct 15, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.