One of the biggest challenges in keeping project documentation alive is ensuring that task summaries are actually written. Most teams finish a feature or fix a bug, merge the code — and the documentation never makes it into the knowledge base.
Working with AI tools such as Claude can unintentionally make this worse. You invest significantly less time in task execution, move faster, and often forget the details the very next day.
At the same time, Claude does an excellent job summarizing its reasoning process and the changes made in the code. It would be a waste not to store this information somewhere for later review — especially now that it is finally easy to automate.
In this post, I’ll show how to set up an environment where Claude automatically generates summaries for completed tasks, Konso Wiki MCP ingests them as structured content, and a ready-to-use wiki website visualizes the result.
What we are building
We will assemble a simple but powerful documentation pipeline: • Add a Konso MCP server to the Claude workspace • Configure Claude to summarize completed tasks automatically • Store those summaries as wiki pages in Konso CMS • Build a fully functional wiki website using Astro
Prerequisites
• A Konso account • If you don’t have one yet, create it here: https://app.konso.io/auth/register • Claude CLI installed and authenticated • Node.js and pnpm installed • Basic familiarity with MCP concepts
Add Konso MCP server to the Claude workspace
Obtain bucket ID and API key 1. Log in to Konso 2. Navigate to Settings → API Keys 3. Copy your Bucket ID and API Key
Register the MCP server
Add the Konso CMS MCP server to Claude:
claude mcp add \
--transport http \
konso-cms-api https://apis-spb.konso.io/cms/mcp/mcp.json \
--header "x-bucket-id: YOUR_BUCKET_ID" \
--header "x-api-key: YOUR_KONSO_API_KEY"
After this step, Claude will be able to create and manage wiki content directly in Konso via MCP.
Guide Claude to write task summaries
In your project root, add or update the CLAUDE.md file with the following instructions.
This file defines when documentation should be created and how it should be structured.
Wiki Documentation for Completed Tasks
When to create wiki entries:
- When the user explicitly requests: "create a wiki entry for task X" - After completing significant features or tasks (multi-file changes, migrations, new endpoints, or UI updates)
How to create wiki entries:
Use the konso-cms-api wiki.create method via the MCP server.
Before creating the entry, gather all relevant information by reviewing: - Git status for modified or new files - Database migration files and schema changes - Backend controllers and API endpoints - UI changes and new components - New interfaces and repository implementations
Parameters: - title: "Task : " Example: "Task 36: Listing Screenshots Management" - slug: "task-" Example: "task-36" - body: Markdown-formatted content following the structure below - category: Logical grouping (project name or another suitable segmentation)
Required sections in the wiki body:
1. Overview
Brief description and purpose of the task
2. Database Changes
Migrations, new tables, schema updates, entity models
3. Data Access Layer
New interfaces, repositories, and data access logic
4. API Endpoints
New or modified endpoints, HTTP methods, routes, parameters, authorization
5. UI Components
New or updated UI components, pages, or features
6. Technical Details
Dependencies added, security considerations, data flow
7. Files Modified / Created
Complete list of affected files with full paths
8. Testing Recommendations
Key scenarios and edge cases to verify
Once this is in place, Claude will consistently generate structured wiki entries after completing qualifying tasks.
Generate wiki entries
Solve a few tasks or issues in your project as usual.
After task completion, Claude will: • Analyze the changes • Generate a structured summary • Create a wiki entry in Konso automatically via MCP
You should now see new wiki pages appearing in your Konso CMS.
Visualize the wiki with Astro
Clone the Astro-based wiki frontend:
https://gitverse.ru/konso/wiki-astro
Configure access
Edit astro.config.mjs and provide:
• Konso API key
• Bucket ID
Run the project
pnpm install
pnpm dev
Open the local development URL shown in the terminal. You should now see a fully functional wiki website rendering the content generated by Claude.
Result
You now have: • Zero-effort task documentation • Structured, searchable wiki content • An automated pipeline from AI reasoning to developer-facing documentation
This setup turns AI-assisted development into long-term organizational knowledge, not just faster task completion.
No comments are allowed for this post