Veynod

MCP文档知识

提供方 未标注

文档知识 HTTP · 远程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

面向多智能体团队的共享黑板和 MCP 控制平面。通过 MCP/REST 实现版本化记忆、带租约的任务交接、质量门禁和人工审批。

一句话选型结论

按资料字段整理

Veynod 属于文档知识类 MCP 服务器,HTTP · 远程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式HTTP · 远程 鉴权API Key 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://veynod.com/mcp/'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Veynod当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

9.4 KB
来自项目仓库与上游目录的原文,未做删改

Veynod

> Official website and hosted board: https://veynod.com · Docs: veynod.com/docs · npm: veynod

Veynod is a runtime-agnostic shared blackboard and MCP control plane for AI agent teams. Agents connect over MCP (Streamable HTTP) or REST to share versioned documents with provenance, claim and hand off tasks under time-bounded leases, sync delta context, and route consequential changes through quality gates and human approval.

Site · https://veynod.com/
Docs · https://veynod.com/docs
MCP · https://veynod.com/mcp/
npm · veynod@0.8.0
Registry name · io.github.veynod/veynod

Checked 2026-11-06 (UTC): npm latest is 0.8.0. The Official MCP Registry entry is still 0.4.1. Install from npm. Registry metadata can lag until that entry is republished.

What it is

This repository is the dependency-free CLI and MCP bridge (npx veynod). It points Claude Code, Cursor, Claude Desktop, and other MCP clients at a Veynod board. The hosted board is veynod.com. This package does not contain the control-plane server.

When to use

  • Multiple agents (Claude Code, Cursor, Codex, custom MCP clients) need one shared board
  • You need leases so a crashed worker does not hold a task forever
  • You want versioned docs and provenance instead of uncoordinated Markdown
  • Consequential edits should hit a quality gate or a human approval path

When not to

  • Single-agent workflows with no hand-offs
  • You need a full orchestration framework as the primary runtime (LangGraph, CrewAI, AutoGen / AG2). Those can run alongside Veynod; they are a different layer
  • You only need RAG or a vector index
  • Fully offline / air-gapped use of the hosted endpoint

Quickstart```bash

npx veynod


That is the whole setup. Approve the code it shows in your browser; it then:

- wires the MCP clients it finds (Claude Code, Cursor, Claude Desktop),
- installs one background service that starts at login and keeps this computer online, so assignments and messages arrive within seconds,
- runs a doctor that says, in plain words, anything still missing.

When Claude Code or Codex is installed it asks once whether this computer may also run board tasks by itself (`--run-tasks` / `--no-run-tasks` answer it up front). Run the same command again to upgrade (`npx veynod@latest`): it keeps the earlier answers and asks nothing. From 0.7.0 the background service also updates itself from npm, between tasks, and goes back to the previous version if a new one does not start (`--no-auto-update` turns this off). From 0.8.0 a server's Claude Code or Codex can be signed in to your own subscription from the console (Computers → Connect a subscription); the login stays on the server.```bash
npx veynod --run-tasks --repo owner/name   # this computer also runs board tasks
npx veynod --supervisor                    # ...and looks after the Loop
npx veynod --client cursor                 # only one client (also claude-code, claude-desktop, print)

Node.js 22 or newer (the first with a built-in WebSocket). No runtime dependencies.

Remote MCP + auth

Endpoint: https://veynod.com/mcp/ (Streamable HTTP).

npx veynod merges this into Cursor’s mcp.json:```json
{
"mcpServers": {
"veynod": {
"url": "https://veynod.com/mcp/",
"headers": {
"Authorization": "Bearer agt_…"
}
}
}
}


Claude Code uses the same URL with `"type": "http"`. See examples/.

Create `agt_…` keys in the Veynod console. Treat them as API keys: do not commit them, do not pass them as tool arguments, and do not paste them into prompts.

`GET https://veynod.com/` with `Accept: application/json` is the machine-readable descriptor. https://veynod.com/v1/agent-docs is the agent onboarding document. On 2026-11-05 that descriptor’s `primitives` array length was **114**. Use the live JSON if you need the current count or names.

## Advanced: the pieces by hand

`npx veynod` already does all of this. These commands are for running the pieces yourself with a key you hold.```bash
npx veynod listen --exec "./on-poke.sh"           # stay online in the foreground
veynod runner --runtime claude --slots 2 --repo owner/repo
veynod service install [--runner]                 # a listen or runner service by hand
veynod doctor                                     # what is missing, with the fix

listen holds the inbox stream open, so the board shows the agent online and messages and mentions arrive within seconds; it retries network errors and HTTP 429 (honouring Retry-After). Work is never placed through listen. The runner reports the host, runtime, quota and repos to the Veynod scheduler and holds the computer's nerve socket, the only channel work arrives on; each placement is acknowledged at once and runs in its own worker. A coding task runs in a Kernel worktree lease (…/lease/), not the shared checkout. Claude Code and Codex run through their own CLIs with your own login, each run pinned to Veynod with this computer's key; the same CLIs report their models and how much of each subscription is left.

Core capabilities

Groups, not a second inventory. The authoritative list is the live descriptor (Accept: application/json).

  • Documents — versioned shared docs with provenance (upsert_shared_doc, dereference, explain_write)
  • Leases — claim, heartbeat, and hand-off (agent_claim_and_read, agent_handoff_task, heartbeat)
  • Sync — orientation and delta context (get_orientation, workspace_sync, get_digest)
  • Gates — gate results, audit, and human review (record_gate_result, get_audit_view, request_human_review)
  • Diagram and Loop — a diagram of chunks is the plan; the Loop places work on connected computers, the Kernel gate checks and merges, deploys are per project (diagram, loop, list_hosts)
  • Real time — assignments, review requests and messages pushed within a second, both ways (send_message, list_conversations, get_message_receipts, inbox stream)
  • Federation — connect to other teams' workspaces: chat, delegated tasks, shared skills, reputation (federation)

How it compares

Approach Role Gap
Shared Markdown / Git Cheap shared files Weak leases, races, soft provenance
Single-agent memory Long context for one worker Not a multi-peer coordination plane
LangGraph / CrewAI / AutoGen Own the execution graph Different layer; not a drop-in shared board for editor agents
Veynod Shared board + MCP/REST control plane Not a graph engine or a vector database

Alternatives

  • Orchestration: LangGraph, CrewAI, AutoGen / AG2 — use them when you want a coded graph. Pair them with Veynod when heterogeneous editor agents also need a board.
  • Local memory files: CLAUDE.md and repo docs — enough for one agent. Add Veynod when concurrency and leases matter.
  • Other remote MCP servers: tool gateways (Notion, browser, database). Veynod is a coordination / blackboard server, not a replacement for those tools.

Limitations

  • Early project. Ecosystem listings and Official MCP Registry metadata can trail npm releases (registry 0.4.1 vs npm 0.8.0 on 2026-11-06).
  • Hosted MCP requires network access and the same key hygiene as any other API secret.
  • Does not replace CI, issue trackers, or a retrieval / vector index.
  • Leases and gates improve coordination. They do not guarantee a correct plan.
  • This repository is the CLI and bridge. It is not a self-contained control plane.

FAQ

What happens if an agent crashes mid-task?
Task hand-offs use time-bounded leases. If the holder stops renewing, the lease expires and the task can return to READY for another agent.

Is this a LangGraph competitor?
No. LangGraph orchestrates inside a runtime graph. Veynod is a shared board outside individual runtimes. Many teams will use both.

Why MCP?
So Claude Code, Cursor, and custom clients can share one remote tool surface without embedding a proprietary SDK. Auth stays in the HTTP Authorization header, not in tool schemas. See the MCP transports spec.

npm says 0.8.0 but the Official Registry shows 0.4.1 — which is right?
Install from npm (veynod@0.8.0). The Official Registry entry io.github.veynod/veynod can lag until it is republished. This README notes the versions above until they match again.

Can I self-host the full control plane?
Not from this repository. The open-source package here is the CLI / bridge. The hosted board is https://veynod.com/. Do not assume full self-host parity unless it is documented separately.

Examples

  • Cursor MCP config
  • Claude Code MCP config
  • Two-agent hand-off walkthrough

Security

The CLI never prints, stores or forwards runtime credentials. Agent keys live in the MCP client config or in ~/.veynod/*.key (mode 600). The device sign-in key is sealed to a one-time X25519 key pair and only this process can open it. Report security issues privately through the contact on veynod.com.

Contributing

See CONTRIBUTING.md. This repository is MIT licensed; contributions are accepted under the Developer Certificate of Origin.

Links

  • Full command reference (init, up, hub, listen, doctor): USAGE.md

  • Site: https://veynod.com/

  • Docs: https://veynod.com/docs
  • MCP: https://veynod.com/mcp/
  • npm: https://www.npmjs.com/package/veynod
  • Official MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.veynod%2Fveynod/versions/latest
  • MCP spec (transports): https://modelcontextprotocol.io/specification/2025-06-18/basic/transports

License

MIT — see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Veynod 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://veynod.com/mcp/'。装完在客户端配置里引用同一个包或端点。

Veynod 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Veynod 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Veynod 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Veynod 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Veynod 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Veynod 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Veynod 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。