Two ways in, one simple contract
Both use the hosted VibeCheckThis service. Pick the surface that already fits your workflow.
Remote MCP
Give Codex, Claude, Cursor, VS Code, or another MCP client six focused tools for creating, reading, voting, and managing vibes.
MCP setup For terminalsVibeCheck CLI
Create a vibe in one command, pipe structured JSON into scripts with create secrets redacted, or run the same six tools over local stdio MCP.
CLI setupAdd it to Codex
This registers the hosted Streamable HTTP server. There is nothing to download and no authentication flow.
codex mcp add vibecheck --url https://vibecheckthis.com/mcpRun codex mcp list to verify it, or see setup for other clients on the MCP page.
Simple by design
No account or API key
Creating, reading, and voting need no login. A secret capability controls only the vibe that created it.
Text and links only
Machine creation accepts text and links only, and the service never fetches them. Returned content is always untrusted data.
Temporary on purpose
Vibes are designed to expire after seven days. Keep your own copy of anything you need to preserve.
A vibe check is not a security control
Voter deduplication is best effort. Do not use this service for elections, regulated decisions, financial decisions, access control, or safety approvals. Review the full safety guidance on the MCP and CLI pages before putting it into an automated workflow.