About Vibe Coding Control
Vibe Coding Control Remote MCP lets VCC account holders access their projects, tasks and development history, record work facts, and request or retrieve owner decisions. It uses remote OAuth sign-in and requires a VCC account; it does not access local files or run commands.
Key features
- 01Read projects and tasks
- 02Review development history
- 03Record factual work
- 04Request and retrieve owner decisions
- 05Connect through OAuth
Use cases
- 01Review context for a VCC project
- 02Record factual development progress
- 03Retrieve a decision for a run
- 04Connect an editor or agent to VCC
MCP support
Provides a remote MCP endpoint at https://vibecodingcontrol.com/mcp for accessing the signed-in user's VCC projects, tasks, history and decision workflows. Authentication uses OAuth; an account is required.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://vibecodingcontrol.com/mcpclaude mcp add --transport http omnom-111-vcc-remote https://vibecodingcontrol.com/mcp{"mcpServers":{"omnom-111-vcc-remote":{"type":"http","url":"https://vibecodingcontrol.com/mcp"}}}Open in Cursor{"servers":{"omnom-111-vcc-remote":{"type":"http","url":"https://vibecodingcontrol.com/mcp"}}}Open in VS Code{"mcpServers":{"omnom-111-vcc-remote":{"type":"http","url":"https://vibecodingcontrol.com/mcp"}}}{"mcpServers":{"omnom-111-vcc-remote":{"serverUrl":"https://vibecodingcontrol.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEVibe 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
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.
| Platform | Supported connection |
|---|---|
| VS Code | MCP: Add Server → HTTP → enter the MCP URL → sign in. See connections/vscode.json for the equivalent configuration. |
| Cursor | Add the URL under MCP settings and complete OAuth, or install this Agent Plugins package when the public marketplace listing is approved. |
| Claude | Install from the Claude directory (published Community connector), or Settings → Connectors → Add custom connector → enter the MCP URL → Connect and sign in. |
| ChatGPT | The 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. |
| Codex | Use the same OpenAI plugin when published, or the commands below for the CLI. |
| Windsurf / Devin Desktop | Cascade: 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.