Cvm: Stateful Programable Task Engine

Created By
LadislavSopkoa year ago
Stop Claude from losing track. CVM is a passive state machine that Claude queries for tasks, maintaining perfect execution flow across complex operations. The Problem "Claude, analyze these 1000 files and create a report" → Claude gets confused, loses context, forgets what it's doing. The Solution CVM is a passive MCP server that holds program state. You write a program with loops and logic, but Claude only sees one task at a time. Claude asks "what's next?", completes the task, and asks again. The magic: CVM never pushes tasks. Claude pulls tasks when ready, maintaining perfect control while CVM quietly manages state between requests.
Overview

What is CVM?

CVM is a stateful programmable task engine designed to help Claude manage complex operations without losing context. It acts as a passive state machine that Claude queries for tasks, ensuring a smooth execution flow.

How to use CVM?

To use CVM, integrate it into Claude's environment by adding it to the .mcp.json configuration. You can then write programs that utilize CVM's task management capabilities, allowing Claude to pull tasks as needed.

Key features of CVM?

  • Passive state management for task execution
  • Supports loops and conditional logic in task definitions
  • Maintains variables and execution state between tasks
  • Allows Claude to process tasks one at a time without losing context

Use cases of CVM?

  1. Document analysis pipelines where multiple files need to be processed sequentially.
  2. Data extraction tasks that require systematic processing of inputs.
  3. Report generation that involves summarizing multiple data sources.
  4. Any workflow requiring AI processing with loops and conditions.

FAQ from CVM?

  • Can CVM handle complex workflows?

Yes! CVM is designed to manage complex workflows by maintaining state and allowing Claude to focus on one task at a time.

  • Is CVM easy to integrate?

Yes! Simply add it to Claude's configuration and start using it with your programs.

  • What programming language does CVM support?

CVM executes a TypeScript-like language, allowing for variables, loops, and conditions.

Server Config

{
  "mcpServers": {
    "cvm": {
      "command": "npx",
      "args": [
        "cvm-server@latest"
      ],
      "env": {
        "CVM_STORAGE_TYPE": "file",
        "CVM_DATA_DIR": ".cvm"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
LadislavSopko
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago