starlog-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@starlog-mcpstart a new session for my-app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

STARLOG MCP
STARLOG (Session, Task, and Activity Record LOG) is a comprehensive documentation workflow system designed for Claude Code integration via the Model Context Protocol (MCP).
Overview
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
Related MCP server: mcp-codex-dev
Features
🏗️ Project Initialization
Automated project setup with registry creation
Integrated starlog.hpi file generation
Context-aware project configuration
📏 Rules System
Hierarchical rule management with categories and priorities
Brain-agent enforcement integration
Dynamic rule validation and compliance checking
📓 Debug Diary
Real-time development issue tracking
Direct GitHub Issues API integration
Automatic bug report and fix workflow
📋 Session Management
Comprehensive session START/END tracking
Goal-oriented work sessions with outcomes
Historical context preservation
🧭 HPI (Human-Programming Interface) System
Automatic context assembly from latest session + debug diary
Project orientation for seamless context switching
Documentation-driven development workflow
Installation
[Installation instructions pending PyPI publication]
Quick Start
Initialize a STARLOG Project
from starlog_mcp import Starlog
starlog = Starlog()
result = starlog.init_project("my_project", "My Project Name")
print(result)Add Project Rules
result = starlog.add_rule("Always write tests", "my_project", "testing")
print(result)Start a Development Session
session_data = {
"session_title": "Feature Implementation",
"start_content": "Implementing user authentication",
"context_from_docs": "Based on security requirements doc",
"session_goals": ["Add login", "Add logout", "Add password reset"]
}
result = starlog.start_starlog(session_data, "my_project")
print(result)Get Project Context
context = starlog.orient("my_project")
print(context) # Complete project context for AI assistanceMCP Server Usage
STARLOG includes a built-in MCP server for Claude Code integration:
starlog-serverEnvironment Variables
HEAVEN_DATA_DIR: Directory for STARLOG data storage (default:/tmp/heaven_data)OPENAI_API_KEY: Required for brain-agent rule enforcement
MCP Configuration
Add to your Claude Code configuration:
{
"mcpServers": {
"starlog": {
"command": "starlog-server",
"env": {
"HEAVEN_DATA_DIR": "/path/to/your/data",
"OPENAI_API_KEY": "your-openai-key"
}
}
}
}Available MCP Tools
init_project(path, name)- Initialize new STARLOG projectrules(path)- View all project rulesadd_rule(rule, path, category)- Add new ruleupdate_debug_diary(diary_entry, path)- Add debug diary entryview_debug_diary(path)- View debug diarystart_starlog(session_data, path)- Start new sessionview_starlog(path)- View session historyend_starlog(session_id, end_content, path)- End sessionorient(path)- Get complete project contextcheck(path)- Check project status
Development
Running Tests
pytest tests/Development Installation
pip install -e .[dev]Architecture
STARLOG uses the HEAVEN framework's registry system for persistent storage and provides a clean FastMCP-based server implementation for seamless Claude Code integration.
Registry Pattern
Data is stored in isolated registries per project:
{project_name}_rules- Project rules with enforcement metadata{project_name}_debug_diary- Development tracking entries{project_name}_starlog- Session history with goals and outcomes
License
MIT License - see LICENSE file for details.
Contributing
Contributions welcome! Please see CONTRIBUTING.md for guidelines.
This server cannot be deployed
Maintenance
Related MCP Connectors
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Claude Code / MCP skills for the dev pipeline: discover, spec, design, build, ship, operate.
Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.
Give your AI agent persistent, governed memory for every project. At task start it recalls the approved decisions, conventions, risks and architecture (semantic search, ranked by importance); at close it proposes what was learned as typed memories that you review and approve — governance, not a notes dump. Agents propose, humans govern: edits go back to pending and deletion is human-only by design. Connect Claude Code, Cursor, Claude Desktop or any MCP client in two minutes with just your API key — hosted (nothing to install) or locally via `uvx solucortex-mcp`. Built by SoluAI and dogfooded daily: SoluCortex is developed using its own living memory.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to manage software development projects with complete context awareness and code execution through Docker environments.8 npm4-
- AlicenseAqualityFmaintenanceAn MCP server that integrates Codex CLI into Claude Code workflows for code writing, execution, and review with session management. It features real-time progress monitoring via a local HTTP dashboard and supports detailed configuration for various coding tools.615 npm166MIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.47187 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that makes project documentation instantly accessible in Claude Code through @ mentions, allowing Claude to understand your codebase's conventions and architecture.5MIT