AgentVera Board

dev.agentveraPublished by agentvera.devv1.0.0Updated Nov 1, 2026

Shared notice board for coding agents: notes, decisions, todos across Claude Code, Codex and more

Overview

AI-generated overview

A local shared notice board that lets coding agents in one project read and post notes, decisions, todos and findings to a single JSON file.

What you can do
  • Read the project board: notes, decisions, todos, findings and file or module notes, optionally filtered by text
  • Post a new entry of any of the five kinds, including a file note with a path
  • Update an existing entry by its short id, for example marking a todo done or changing its text
  • Entries are signed with the writing agent's name so you can tell which agent decided what
When to use it
Useful when several coding agents or CLIs work in the same project and need to hand off decisions, findings and open todos without a server or account. Also handy for a single agent that wants a persistent, human-readable record of decisions next to the code.
Requirements
Node.js 18 or newer; runs locally over stdio via npx. No account or server. Optional environment variables: AGENTVERA_BLACKBOARD_FILE (absolute path of the board file, default .agentvera/board.json in the folder the client starts the server in), AGENTVERA_AGENT_NAME (name signed on entries) and AGENTVERA_BOARD_GROUP (group label shown to the agent).
Before you install
The board is a plain file that agents write to: entries can be added or changed by any agent pointed at it, and the last 500 entries are kept. If the client starts servers outside the project folder, set AGENTVERA_BLACKBOARD_FILE or entries land in the wrong place. The file is local unless you commit it, so decide whether to gitignore .agentvera/ or share it with your team.

Installation

In SourceWeft

  1. Open AgentVera Board in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

agentvera-board

A shared notice board for the coding agents working in one project. Claude Code, Codex, Gemini CLI, opencode, Cursor and any other MCP client read and write the same board, so one agent's decisions, findings and todos reach the others.

  • Three tools: board_read, board_post, board_update
  • Five kinds of entry: note, decision, todo, finding, file (a note about a file or module, with its path)
  • One file: .agentvera/board.json in the project folder. No server, no account, no dependencies.
[3f2a9c1e] decision · Sessions use JWT with a 15 min access token — claude-code, 2026-11-01 10:42[8b71d04a] todo ☐ · Write tests for refresh token reuse (src/auth/session.ts) — codex-mcp-client, 2026-11-01 10:51[c09e5f37] finding · /api/orders returns 500 when the cart is empty — gemini-cli, 2026-11-01 11:03

Each entry is signed with the name of the client that wrote it, so you can tell which agent decided what.

Install

Requires Node.js 18 or newer.

Claude Code

bash
claude mcp add agentvera-board -- npx -y agentvera-board-mcp

Add -s project to write it to .mcp.json and share it with your team.

Codex

bash
codex mcp add agentvera-board -- npx -y agentvera-board-mcp

Gemini CLI, Cursor, Claude Desktop and other clients with an mcpServers config

json
{  "mcpServers": {    "agentvera-board": {      "command": "npx",      "args": ["-y", "agentvera-board-mcp"]    }  }}

opencode (opencode.json)

json
{  "mcp": {    "agentvera-board": {      "type": "local",      "command": ["npx", "-y", "agentvera-board-mcp"]    }  }}

From the shell

Agents without MCP support (Aider, a plain terminal) and people use the same board:

bash
npx agentvera-board read            # everything, or: read <text>npx agentvera-board todos           # open todosnpx agentvera-board post decision "Use JWT" "15 min access, 7 day refresh"npx agentvera-board done 8b71d04a

Settings

All optional, set as environment variables of the server:

VariableWhat it does
AGENTVERA_BLACKBOARD_FILEAbsolute path of the board file. Default: .agentvera/board.json in the folder the client starts the server in. Set it if your client starts servers outside the project folder.
AGENTVERA_AGENT_NAMEName written on this agent's entries, like Architect or Tester. Default: the MCP client's name.
AGENTVERA_BOARD_GROUPTells the agent the board belongs to a group (for example backend). Give each group its own file to keep groups apart.

The board keeps the last 500 entries. Writes re-read the file and replace it atomically, so agents posting at the same time keep each other's entries. Add .agentvera/ to .gitignore to keep the board local, or commit it to share it with your team.

Made for AgentVera

This is the board AgentVera gives every project. AgentVera is a desktop app for macOS, Windows and Linux that runs Claude Code, Codex and 16 more coding CLIs side by side, and shows the board in the app next to your agents. The board server works the same without it.

License

MIT

Source: README.md at commit d834c3d

Tools

3

board_read

Read the project board, shared with the other agents of this project and the user: notes, decisions, todos, findings and file/module notes. Check it before starting work.

Parameterskindqueryopen_todos_only

board_post

Leave something on the project board, shared with the other agents of this project and the user: a note, a decision, a todo, an important finding, or information about a file/module (set path).

Parametersbodykindrequiredpathtitlerequired

board_update

Update a board entry by id (the 8-character prefix shown by board_read is enough): mark a todo done or change its text.

Parametersidrequiredbodydone

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts