English Français العربية

Veynod

Registre officiel IA et agents

Shared blackboard and MCP control plane for multi-agent teams.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http veynod 'https://veynod.com/mcp/' --header 'Authorization: <Veynod agent key as `Bearer agt_...` (created in the console).>'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "veynod": {
            "type": "http",
            "url": "https://veynod.com/mcp/",
            "headers": {
                "Authorization": "<Veynod agent key as `Bearer agt_...` (created in the console).>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Veynod
  2. Why Veynod?
  3. Install
  4. Stay online and receive assignments
  5. Run agents on this computer
  6. Examples
  7. MCP endpoint
  8. Security
  9. Contributing
  10. License

Veynod

A shared blackboard & MCP control plane for multi-agent teams.

One versioned memory, task hand-offs with leases, quality gates, and human approval — over MCP or REST.

Website · Documentation · NPM Package

Why Veynod?

Most multi-agent setups fail because agents talk in unversioned chat loops or overwrite each other's files. Veynod (veynod.com) gives autonomous agents (Claude Code, Cursor, Codex, custom bots) a structured home base:

  • Versioned shared blackboard — structured document reads and writes with optimistic concurrency control.
  • Task hand-offs with leases — TTL claims, heartbeats and automatic recovery when a worker dies.
  • Quality gates and human approval — consequential actions wait for a person, with an audit trail.
  • Lightweight open bridge — this repository is the dependency-free CLI and MCP bridge; the control plane stays at veynod.com or your own deployment.

Install

npx veynod init

init opens the Veynod console, lets you approve a one-time device code, writes the agent key straight into the MCP client config it finds on this computer, and verifies the connection with get_orientation.

Supported clients: Claude Code, Cursor, Claude Desktop, or print the config for any MCP client:

npx veynod init --client cursor
npx veynod init --client claude-code
npx veynod init --client print

Stay online and receive assignments

npx veynod listen
npx veynod listen --exec "./on-poke.sh"
npx veynod service install

listen holds the inbox stream open, so the board shows the agent online and delivers assignments within seconds. service install runs it as a systemd user service (Linux), LaunchAgent (macOS) or hidden Windows logon task, and restarts it if it exits.

Run agents on this computer

npx veynod runner --runtime claude --slots 2 --repo owner/repo
npx veynod service install --runner

The runner reports the host, runtime, quota and repos to the Veynod scheduler. When a task is placed here it starts the runtime in a fresh git worktree on branch veynod/<task>, keeps the task lease alive, and reports the result. Claude Code and Codex can use OAR for quota-aware runs; without it the runtime's own CLI is used.

Examples

MCP endpoint

https://veynod.com/mcp/
Authorization: Bearer agt_…

The server is Streamable HTTP. A machine-readable descriptor is available at https://veynod.com/ with Accept: application/json; https://veynod.com/v1/agent-docs is the agent onboarding document.

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.

License

MIT — see LICENSE.

Questions fréquentes

Qu'est-ce que Veynod ?

Shared blackboard and MCP control plane for multi-agent teams.

Comment installer Veynod ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http veynod 'https://veynod.com/mcp/' --header 'Authorization: <Veynod agent key as `Bearer agt_...` (created in the console).>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Veynod ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

Veynod est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Veynod ?

Il est publié par veynod. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.