viqueue

viqueue

Enables agents and humans to manage a central ticket dispatcher via MCP, with tools to create, claim, renew, takeover, and submit tickets through a local HTTP server.

Category
Visit Server

README

viqueue

viqueue is a minimalist pull-based ticket dispatcher for agents and humans. The CLI is viq; ticket IDs look like ABC-123. v0.3.0 is an unpublished prerelease for local evaluation.

Daily Alpha contract

The HTTP JSON core is the only state machine. viq, MCP stdio, and the browser are thin HTTP clients. Runtime data lives in one SQLite file using Node 22's built-in node:sqlite and normalized projects, tickets, claims, events, actors, roles, actor-role memberships, and questions.

Tickets have only open, review, and done states. Registered actors and roles provide typed actor/role assignment. Active agents may claim unassigned work; assigned work requires matching actor or role membership. Claim owners can ask fenced questions while continuing progress, and submission explicitly targets a reviewer whose approval answer atomically accepts or requests changes. The board projects them as Ready (open without a claim), Working (open with a claim), Review, and Done.

A claim persists until an explicit release, submission, or takeover. Silence changes nothing. Claims are authority locks, not liveness. Claim identity contains an opaque claim_id, actor, generation, and an unguessable token whose hash—not plaintext—is stored. Executor mutations require all current credentials. Explicit local-operator takeover increments generation and fences every older owner.

Progress events are observations, not proof of liveness. Events form append-only per-ticket and global streams with a monotonic cursor. Agents pull work; viqueue never starts workers.

Run

Requires Node.js 22. Runtime has no third-party dependencies; Playwright is development-only.

npm test
npm run build
VIQ_OPERATOR_TOKEN=local-secret node dist/src/server.js --storage=./data/viqueue.sqlite

Open http://127.0.0.1:7373 for the responsive four-column board and prominent Questions for you inbox. The persisted actor selector is private-alpha workflow context, not authentication; server-side actor/role eligibility is still enforced.

Representative CLI operations:

viq actor create eva --name Eva --kind agent --machine tower-pi --auth TOKEN
viq actor show|update|deactivate eva; viq role grant|revoke eva reviewers --auth TOKEN
viq project create ABC                 viq project list
viq ticket create ABC "Fix parser" --body "..." --assignee eva
viq ticket list ABC --assignee eva     viq ticket show ABC-1
viq ticket edit ABC-1 --assignee-role builders
viq ticket next --project ABC          viq ticket claim ABC-1 --actor eva
viq question ask ABC-1 <claim credentials> --text "Need input" --target-role reviewers
viq question answer ABC-1 Q --actor maks --answer "yes"
viq ticket submit ABC-1 <claim credentials> --reviewer-role reviewers
viq ticket takeover ABC-1 --actor maks --auth LOCAL_TOKEN
viq ticket accept|reopen ABC-1 --actor maks --auth LOCAL_TOKEN
viq event post ABC-1 <claim credentials> --message "tests green"
viq event list --project ABC --after CURSOR

CLI JSON mode writes one JSON document. Exit codes are 0 success, 2 usage, 3 conflict, 4 not found, 5 other HTTP error, and 6 client/transport error. MCP exposes coherent equivalents through tools/list; run viq-mcp with VIQ_URL (legacy VIQ_SERVER is also accepted). VIQ_OPERATOR_TOKEN is only needed for operator tools. The actor selector and actor fields are private-alpha workflow identity, not adversarial authentication: keep HTTP behind a trusted loopback or private Tailscale boundary and never expose it with Funnel/public ingress.

Import v0.2 JSON safely

The server never silently interprets or discards an old JSON file. Create a new SQLite file explicitly:

viq-import --from ./data/viqueue.json --to ./data/viqueue.sqlite

The one-shot importer preserves project keys, next numbers, ticket IDs/titles, submitted review state, evidence as an import event, and legacy claim fencing credentials. A legacy current claim is imported as a durable current claim with the same actor, generation, and token authority. Submitted tickets release their old claim. If any claim lacks actor, generation, or token, import fails closed and removes the incomplete target. Existing targets are never overwritten. Keep the old JSON backup until validation is complete.

Local bundle and evidence

npm run bundle creates deterministic release/viqueue-v0.3.0-rc.tar.gz plus SHA-256. Its reversible installer adds viq, viq-import, viqueue-server, and viqueue-mcp under ${VIQ_PREFIX:-~/.local}; uninstall preserves separately located ticket data. Nothing here publishes, pushes, tags, deploys, or launches workers.

npm run e2e exercises CLI, MCP, and Chromium and writes evidence/screenshots when VIQ_EVIDENCE_DIR is set. See ADR 0008, CHANGELOG.md, and release notes.

viqueue is licensed under the Apache License 2.0. See CONTRIBUTING.md and SECURITY.md.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured