Starlog MCP Server

Most knowledge and memory work still happens through a UI a human drives. Starlog MCP server moves it into the conversation instead. STARLOG documentation workflow MCP for Claude Code integration.

The short version

STARLOG (Session, Task, and Activity Record LOG) is a comprehensive documentation workflow system designed for Claude Code integration via the Model Context Protocol (MCP).

STARLOG provides three integrated documentation types: - RULES: Project guidelines with brain-agent enforcement - DEBUG_DIARY: Real-time development tracking with GitHub issue integration - STARLOG: Session history with START/END markers for context continuity

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: HEAVEN_DATA_DIR, OPENAI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Isaac and Claude; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Starlog's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.