How to Keep Your Knowledge Base Updated with Claude Code

You keep a knowledge base updated with Claude Code by connecting FeatureOS over MCP, listing collections and articles from the terminal, then comparing live help content to completed feature requests and changelogs after every ship. The goal is a five-minute docs check, not a quarterly rewrite project.

Shipping is easy to see. Docs rot quietly. A feature lands, the changelog goes out, support still pastes the old answer, and the knowledge base lags a sprint behind reality. Claude Code is already where you finish the work. FeatureOS holds the articles customers actually open.

TL;DR: Add https://mcp.featureos.app/mcp to Claude Code, OAuth once, then list collections, open full article content, and gap-check against recent changelogs and posts. Ground every rewrite in fetched FeatureOS content so Claude does not invent UI labels.

This is part three of a three-post series:

1. How to manage feedback via Claude Code
2. How to manage changelog via Claude Code
3. How to keep your knowledge base updated with Claude Code (this post)

Why does knowledge base content fall behind the product?#

Knowledge bases fall behind because docs are treated as a separate project from shipping. Typical lag: feature merges, changelog maybe publishes, support invents a workaround, someone files a "docs todo," and weeks later the article is still wrong. Teams usually have a help center. They lack a habit of updating it in the same window as the release.

MCP will not write perfect docs alone. It removes the excuse that FeatureOS is "another app." You can query the KB next to the PR and the board.

What can Claude Code read from your FeatureOS knowledge base?#

The public FeatureOS MCP server exposes list and get operations for articles and collections. You can filter by status, language, collection, assignee, author, privacy, and tag; open full article content; and browse parent and sub-collections. You can also pull feature requests and changelogs on the same connection to source what customers asked and what you announced.

From the FeatureOS MCP integration:

Articles#

• List articles filtered by status, language, collection, assignee, author, privacy, and tag
• Get an article with full content, authors, assignees, tags, and collection

Collections#

• List collections, optionally by parent (sub-collections)
• Get a collection with metadata and article count

Workspace context that feeds better docs#

• Feature requests (list, get, comments) for "what customers asked"
• Changelogs (list, get, search) for "what we announced"
• Tags, boards, team members for ownership and structure

Note: Article create/update/publish paths can differ between FeatureOS surfaces (in-product agent vs public MCP). Treat MCP as the live read and research layer for KB, and confirm write tools in your client before you assume publish-from-terminal. The workflow below is built around list, get, and collections.

How do you connect Claude Code to FeatureOS for docs work?#

Use the same MCP URL as feedback and changelog management. One OAuth session covers all three.

https://mcp.featureos.app/mcp

{
  "mcpServers": {
    "featureos": {
      "type": "http",
      "url": "https://mcp.featureos.app/mcp"
    }
  }
}

Verify:

List published articles in the Getting Started collection.

List the sub-collections under the main Help collection.

Real titles and structure mean you are connected.

How do you run a docs-maintenance workflow in Claude Code?#

A sticky workflow is: map your collection → open the article customers hit → diff it against changelogs and posts → turn repeat how-to feedback into doc tasks → run a five-minute check after every meaningful ship. That sequence keeps help content aligned with the product without a separate "docs week."

1. Map the collection you own#

List collections in our knowledge base.

Get collection <id> and summarize how many articles it holds.

List published articles in the Billing collection.

2. Find the article customers will hit#

Find articles assigned to Sarah about billing.

List published articles tagged "sso".

Get the full content of article 77.

Read the live body before you rewrite from memory. Stale docs often fail in one paragraph: a menu path, a plan name, a removed button.

3. Diff product reality against the article#

List changelogs published in the last 30 days that mention SSO or billing.

Get feature request 101 and its latest comments. Does our KB already answer this?

Get article 77. List every step that might be wrong after v2.4.

Claude is strong at "here is the article, here is what shipped, here are three concrete edits." You still apply the edit in FeatureOS (or via any write tool your client exposes).

4. Turn repeated support into a doc task#

Show posts from the last 60 days that look like how-to questions, not new feature asks.

For each, check whether we already have a published article covering it. List gaps.

That is how self-serve grows: intercept the same question before it becomes ticket volume. See why knowledge bases matter and writing great help center articles.

5. After every meaningful ship, run a five-minute docs check#

We just shipped the work in posts 101 and 102 and published changelog v2.4.
1) List KB articles that mention these features.
2) Open the most relevant article.
3) Propose an updated outline and the exact paragraphs to change.

Five minutes in Claude Code beats a quarterly "docs debt" project.

Which prompts keep a knowledge base healthy?#

The best prompts name collection, status, article ID, and source material (changelog version or post IDs). Never ask for a full guide from model memory alone.

Browse

• List published articles in the Getting Started collection.
• List articles with status draft / in review.
• List sub-collections under Help.
• Get collection <id> with article count.

Read

• Get the full content of article 77.
• Find articles assigned to <name> about <topic>.
• Show articles about billing that are private or unlisted.

Gap analysis

• Compare changelog v2.4 to articles tagged "onboarding". What is missing?
• Get post 1234. Is this a feature request or a docs failure?
• List top feature requests about "export". Do we have a how-to article?

Edit plan (output you paste or apply)

• Rewrite the steps in article 77 for the new Settings > Security layout. Keep the same tone. Mark anything you are unsure about.
• Draft a new article outline: "How to enable SSO with Okta." Use only facts from posts 101-103 and changelog v2.4. Do not invent UI labels.

Hallucinated menu paths are worse than no article. Ground Claude in fetched FeatureOS content. For AI-ready structure, see optimize your knowledge base for AI.

How do feedback, changelog, and KB fit in one loop?#

Same connection as feedback and changelog management. Three jobs: capture, announce, document.

In-dashboard AI Chat still helps when you are already in FeatureOS. MCP is for staying in Claude Code.

What quality bar should AI-assisted help docs meet?#

Before anything goes public: every UI label comes from a real product source, plan and permission language matches current packaging, broken steps are removed, related article links still work, and a human clicks through the flow once. Claude accelerates research and first drafts. You own accuracy.

That bar matters because help content is support infrastructure, not marketing copy. See also the knowledge base lie.

How secure is knowledge base access from Claude Code?#

OAuth uses your FeatureOS permissions, including private articles you can already see. Do not paste secrets into article bodies via any assistant. Revoke under Dashboard → Organization Settings → Advanced when access should end.

How do you troubleshoot missing articles in Claude Code?#

Full connector reference: FeatureOS MCP integration.

Checklist#

1. MCP connected and List published articles in … works
2. Know which collections you own
3. On each ship: find related articles → get full content → produce an edit list
4. Ground rewrites in changelogs + completed posts
5. Human click-through before publish
6. Convert repeat feedback into doc tasks, not only new feature cards

A knowledge base that updates in the same breath as the release is a support strategy, not a side project.

Start a FeatureOS trial, connect MCP, and run the gap-analysis prompts against your real Help collection.

Related Reading#

• How to Manage Feedback via Claude Code: Capture and triage requests from the terminal.
• How to Manage Changelog via Claude Code: Announce what shipped, then update the docs.
• Write Great Help Center Articles: Structure and tone for support content.
• Self-Service Knowledge Base: Why deflection depends on fresh docs.
• Why Knowledge Base: Business case for investing in help content.
• The Knowledge Base Lie: What breaks when docs lag the product.
• Optimize Your Knowledge Base for AI: Structure docs so AI search and assistants can use them.
• FeatureOS MCP Integration: Official setup and tool list.