HuntsDesk

Ve Vibe Board

Name: Ve Vibe Board
Author: HuntsDesk

Productivity community

SOURCE https://github.com/HuntsDesk/ve-vibe-board

Description

Task board and session handoff for Claude Code agents. 14 MCP tools for projects, tasks, sessions, and activity logs, backed by Firestore's free tier. Next session reads the last handoff and resumes — no re-explaining what you were doing.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Vibe Board MCP (ve-vibe-board)

[![MCP server on Glama](https://glama.ai/mcp/servers/HuntsDesk/ve-vibe-board/badges/card.svg)](https://glama.ai/mcp/servers/HuntsDesk/ve-vibe-board) [![Glama Score](https://glama.ai/mcp/servers/HuntsDesk/ve-vibe-board/badges/score.svg)](https://glama.ai/mcp/servers/HuntsDesk/ve-vibe-board) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Node](https://img.shields.io/badge/Node-22%2B-brightgreen.svg)](https://nodejs.org/)

Your agent, but it remembers. Firestore-backed MCP server that gives Claude Code (and any MCP-speaking agent) **persistent memory across sessions** — tasks, progress, decisions, and handoff notes that survive context compaction and session death.

**Companion repo**: [`HuntsDesk/ve-kit`](https://github.com/HuntsDesk/ve-kit) — Vibe Coding Framework & Persistent Memory for Claude Code. ve-kit bundles this MCP server, a RIPER-CAT workflow, review-gate hooks, and an optional Docker worker.

**Part of [Vibe Entrepreneurs](https://vibeentrepreneurs.com)** — a community for any vibe coders shipping real work with AI. Come say hi: **[vibeentrepreneurs.com](https://vibeentrepreneurs.com)**.

Why this exists

Sound familiar?

You're six tool calls into a refactor. Context compacts. The agent comes back with vibes but no plan.
You start a new session tomorrow. It re-reads the same files, re-asks the same questions, re-decides things you already decided.
You watched it write a perfect TodoWrite checklist — then the conversation ended, and the checklist evaporated with it.
You opened three agents in parallel. None of them know what the others did.

This is what statelessness feels like in practice. The agent is brilliant for an hour and amnesiac forever after.

Vibe Board is where the state goes instead. It's a shared task + session board that lives outside any single conversation — in Firestore, not in context.