Editorial status · ActiveUpdated 2026-09-07

Dev Knowledge Base

Organize recurring development, deployment, and operations decisions so Codex can reuse the same guidance and project material in everyday personal development.

Core idea Shared guidance lives in a Markdown wiki; project status and public descriptions live in the archive database. One MCP connection provides scoped reading, editing, and requested service checks.

  • Markdown
  • TypeScript
  • Vue
  • Node.js
  • SQLite
  • Go
  • MCP
  • Docker
  • Coolify

In active personal use

Dev Knowledge Base collects development, deployment, and operations guidance for reuse in Codex tasks. It is used in everyday personal development and operations and has moved from MVP evaluation to the personal services collection.

Shared guidance and project material

The TypeScript/Node.js MCP gateway provides index, search, and document-reading tools for the Markdown wiki. Shared guidance stays in the wiki; project goals, status, work records, and public descriptions stay in the connected archive. Codex reads them through one MCP connection and compares the guidance with the target project's actual code, versions, and environment.

Scoped edits and requested status checks

The management web app and device-specific MCP tokens control access. Explicitly authorized tools can edit the wiki and archive. Wiki edits use SHA-256 conflict checks, backups, and auditing; archive database edits check revisions and preserve previous values.

A request to update a specific project or all projects also collects linked Coolify service status. Startup and periodic timers do not collect status. Archive names, descriptions, and Markdown are available on the next request after a database save; only feature-code changes require a build and deployment.

Operations and ongoing checks

The service runs in Coolify containers on a personal Ubuntu server, with a Vue management UI and SQLite authentication and audit storage. Ongoing checks cover document freshness, connections across PCs, edit conflicts, and backup recovery. Secrets and internal connection details are excluded from the public description.

FEATURES / VERIFIED

Core features

  • Wiki index, search, document reading, and permission-scoped editing
  • Device-specific MCP tokens and resource/tool approval in the management web app
  • Archive projects, records, and linked material through one gateway
  • Requested updates for a specific project or all projects together with Coolify status
  • Database updates for public archive descriptions with conflict checks and preserved previous values

Operations and access

Operations status check · Stale information

Execution: Running · Health: Healthy · Latest deployment: Succeeded

Checked:

Last success:

Open service ↗ Hosting · Personal Ubuntu server · Coolify · Node.js MCP gateway

PricingA tool for personal development and operations; no sales price applies to this listing.

FAQ / VERIFIED

Frequently asked questions

Is the service already in use?
Yes. I use it in personal development and operations to retrieve shared guidance and manage project material and work records.
Can Codex edit the wiki and project information?
Yes, through explicitly authorized tokens and tools. Read and write permissions are separate, and wiki and public-content edits use conflict checks and preserve previous content.
Does Coolify status update automatically?
No. It is checked when Codex is asked to update a specific project or all projects. Archive descriptions are stored in the database, so content edits do not require redeployment.