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.
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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。