50 First Tapes MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
50 First Tapes
An open, local-first knowledge engine. Your notes are plain markdown and git — the tapes; your AI reads and writes them behind governance gates. No lock-in: git clone and walk away.
Apache-2.0 · OKF-compatible · TypeScript. The v1 protocol verbs work today. This repo is the engine and carries no personal data.
Why
Knowledge that outlives any one tool or chat, that an AI agent can read and write safely, and that you can build products on — a personal vault, a team wiki, an agentic LMS. The field converged on this pattern in 2026 (Karpathy's LLM wiki, Google's Open Knowledge Format). 50 First Tapes adds the hard parts those leave out: trust, governance, multi-agent writes, and a typed schema system.
Related MCP server: Link
The layers
Products & views — your vault · a team wiki · an agentic LMS
Agents & governance — crew + rules as data; gates; audit; the loop runner
Protocol — ingest · query · lint · write · govern (MCP · CLI · library)
Derived index — full-text + vector + graph; rebuilt on demand; never committed
Substrate — markdown + YAML + git; OKF-compatible; the durable floorThe verbs
One protocol, three shapes — a CLI (tapes), an MCP server, and a library. The five verbs:
Verb | What it does |
| Bring raw material in as a governed, kind-scaffolded note. Gates block; schema gaps are reported, not blocked. |
| Find notes by free text (title-weighted), kind, tag, status, or backlinks. Reads on demand — no committed index. |
| Validate every note against its kind, and check structural health: broken/stale links, orphans, committed blobs, hot-core budget. |
| Write exact content to a note id, through the governance gates. |
| Dry-run the gates on proposed content without writing. |
tapes lint # validate the bundle in the current dir
tapes query "vector search" --kind note # find notes
tapes ingest article.md --kind source # file new material under inbox/
tapes govern wiki/draft draft.md # would this write be accepted?Governance. Writes pass gates before they land: an off-limits path (private, secrets) or a credential-like string is refused and nothing is written. Edits are hash-anchored — patch replaces a paragraph by its content hash and is rejected if that content has moved, so concurrent edits never clobber.
Packages
@50firsttapes/core— schema system, validator, structural-health checks, query, ingest, governance gates, hash-anchored edits, OKF read/write.@50firsttapes/cli— thetapescommand:ingest · query · lint · write · govern.@50firsttapes/mcp— a stdio or HTTP MCP server exposing the verbs to any client (Claude Code, Codex, claude.ai). The native tools — read (query/read/list/lint) and gated write (write/patch/govern) — plus wiki-mcp-compatible tools (session_bootstrap,search,read_note,list_folder,get_recent_logs) so it can stand in for the read-only wiki-mcp gateway.@50firsttapes/remote— a git-remote adapter (Forgejo · GitHub · bare). 50 First Tapes depends on git, never on a forge.
Quickstart
pnpm install
pnpm build
node packages/cli/dist/index.js lint examples/sample-bundle
node packages/cli/dist/index.js query --kind note --bundle examples/sample-bundleRun the MCP server over a bundle. Stdio is the default (local clients like Claude Code):
TAPES_BUNDLE=/path/to/bundle node packages/mcp/dist/index.jsFor hosted use, serve over HTTP with Bearer auth (discovery is open; tool calls require a token):
TAPES_HTTP_PORT=8080 TAPES_MCP_TOKEN=sk-… TAPES_BUNDLE=/path/to/bundle node packages/mcp/dist/index.jsSource of truth
Forgejo is the canonical remote; GitHub is a one-way push mirror. Contribute via Issues and PRs on GitHub — see CONTRIBUTING.md.
Licence
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Your organization's knowledge as OKF trees in Git, for AI assistants to search, read, and cite
Git-backed platform for skills, tools, and context for AI agents
The second brain your AI agents share. It builds itself from your work and keeps itself current.
Governed, auditable knowledge your team curates for its AI assistants, self-hostable
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely read and write to an Obsidian-compatible Markdown vault with per-agent access control, audit logging, and conflict resolution.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.218MIT
- AlicenseBqualityBmaintenanceEnables AI agents to securely read, search, and write to a local Markdown knowledge base with hybrid RAG retrieval, privacy zones, hash-locked writes, audit logging, and rollback-safe archiving.13MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and maintain a shared, git-backed Markdown wiki: they search, file, update and link notes with YAML frontmatter, keep verbatim sources, and optionally read code repos, so knowledge one assistant records is available to all the others. Runs without LLM calls, embeddings or a database, with the vault's own files defining page types, instructions and tools.MIT