A Model Context Protocol (MCP) server for engineering commit story journal entries.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-wiggitywhitney-mcp-commit-story","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Commit Story: Your Engineering Journey, Remembered ## What is MCP Commit Story? MCP Commit Story is a personal engineering journal for developers who want to capture not just what they built, but how it felt and why it mattered. It's a tool-in-progress, built by and for developers who care about the story behind the code. MCP Commit Story runs as a Model Context Protocol (MCP) server, designed to work hand-in-hand with AI agents. These agents help gather and summarize the real context from your development workflow—so your journal entries are always grounded in what actually happened. --- ## Why Build This? As a developer, it's easy to forget the "why" behind your work—what challenged you, what you learned, and how you grew. MCP Commit Story helps you: - **Capture the narrative:** Each commit becomes a journal entry, recording not just the technical changes, but the decisions, frustrations, and small wins along the way. - **Remember how it felt:** The journal includes mood and emotional context, so you can look back and see not just what you did, but how you experienced it. - **Surface stories and insights:** By collecting real context from your workflow (AI Agent chat, terminal, code changes, commit messages), you can spot threads of challenge and triumph—perfect for blog posts, conference talks, or just understanding your own growth (no small thing!) - **Support retrospectives and reviews:** Summaries and insights make it easier to reflect, ask for career advancement, or explain why certain choices were made. --- ## What Does a Day Look Like? Here's an example daily summary, generated from real development data: ```markdown # Daily Summary - June 4, 2025 ## Summary June 4th was a day of strategic evolution from "making it work" to "making it production-ready" - a journey that revealed the hidden complexities of building robust systems. The day progressed from adding comprehensive MCP best practices to breakthrough insights about AI orchestr…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.