Skip to content

CHT-Docs MCP Server Documentation#2111

Merged
Hareet merged 4 commits intomainfrom
add-docs-mcp-server
Jan 21, 2026
Merged

CHT-Docs MCP Server Documentation#2111
Hareet merged 4 commits intomainfrom
add-docs-mcp-server

Conversation

@Hareet
Copy link
Member

@Hareet Hareet commented Jan 15, 2026

Description

Me and agent Claude created documentation around the CHT-Docs MCP Server. Genspark helped create the image.

Notes:

  • I think I remember we wanted an "AI + CHT" at the top-level section. Feel free to recommend another re-organization of the titles.
  • I tried to add an intro paragraph about AI and it's use with CHT, but wasn't sure if that should live here. I was trying to have something similar to content in the "Why CHT?" section, that answered like why are we trying to implement AI or for what.
  • I wasn't sure if we wanted to nest CHT-Docs under MCP Servers, or have that content just be listed inside the MCP Server category.
    • We'll be getting other MCP servers, so we can always modify that later

… moved them to cht-docs. Created top level AI section and nested KAPA AI mcp server content
@Hareet Hareet changed the title Migrated previously generated documents with AI about MCP Servers and… CHT-Docs MCP Server Documentation Jan 15, 2026
@Hareet Hareet self-assigned this Jan 15, 2026
@Hareet Hareet requested a review from andrablaj January 15, 2026 02:01
@Hareet Hareet moved this to 💻 In Progress in CHT Stewardship Activities Q1 2026 Jan 15, 2026
@Hareet
Copy link
Member Author

Hareet commented Jan 15, 2026

I think I remember we wanted an "AI + CHT" at the top-level section. Feel free to recommend another re-organization of the titles.

Looking at it locally for some time, I think it feels better below the "Technical Overview" section. So perhaps before the "Design" and "Build", people may look through the AI section and see what AI setups may help them design and build?

…be accepted at this placement. Added card to main page.
…ssues' consistent across spelling and style.
@Hareet
Copy link
Member Author

Hareet commented Jan 15, 2026

Using a custom /docs-reviewer command we built with Claude:

Recording.2026-01-14.211931.mp4

@Hareet Hareet requested review from mrjones-plip and sugat009 and removed request for sugat009 January 15, 2026 04:26
@mrjones-plip
Copy link
Contributor

Thanks for reaching out for the review! Since you asked Andra first, I'll wait for her review first and then do mine. (Also just happy to take the review/let her do the review as we normally don't do more than one review per PR)

👀

@Hareet Hareet removed the request for review from mrjones-plip January 15, 2026 11:51
@mrjones-plip
Copy link
Contributor

I thought you had particular feedback about this topic.

Fair!

Copy link
Member

@andrablaj andrablaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have some minor wording suggestions, but nothing is blocking. I am excited about this new category in our Docs Site!

Copy link
Member

@andrablaj andrablaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to approve 😄

@mrjones-plip
Copy link
Contributor

Cool to see!!

Two questions:

  • Should we move the URL to app? I'm actually less concerned about the URL and more concerned that it be in the prod EKS cluster (https://mcp-docs.dev.medicmobile.org/mcp)
  • Is the cht-agent repo up to date? There doesn't seem to be any actual code in there that someone could use to run their own MCP. Feels like we maybe need to merge the 1 PR maybe? I guess if this PR is less "learn to run your own MCP and how we built it" and more "use our MCP" then the other PR should block this one. However, I think it'd be great to merge what ever we're running in production and make it all public!

@mrjones-plip
Copy link
Contributor

Oh - also - if we have duplicate content in our internal repo (private link), we should be sure an delete any duplicates - thanks thanks!

@Hareet
Copy link
Member Author

Hareet commented Jan 21, 2026

Should we move the URL to app? I'm actually less concerned about the URL and more concerned that it be in the prod EKS cluster (https://mcp-docs.dev.medicmobile.org/mcp)

We should move it to app... at a later time. Since it's our first MCP that interacts with AI, I wanted to separate it from any projects and have time to understand observability. At the same time, we wanted to allow people to use it immediately, so it's a better fit on dev and something akin what google would call an beta release.

Is the cht-agent repo up to date? There doesn't seem to be any actual code in there that someone could use to run their own MCP. Feels like we maybe need to medic/cht-agent#7? I guess if this PR is less "learn to run your own MCP and how we built it" and more "use our MCP" then the other PR should block this one. However, I think it'd be great to merge what ever we're running in production and make it all public!

These are separate things. This MCP server brings Kapa AI database into AI Assisted Setups. Following the CHT-Agent architecture, this MCP is the referenced as the documentation agent. The CHT-Agent will be an npm package that you can install, and will need to connect to this MCP server. During our building of the CHT-Agent, we will release the smaller agents as independent functionality that can be used with other off-the-shelf AI tools. Hop into #multi-agent-system-squad and we can detail this further.

Oh - also - if we have duplicate content in our internal repo (private link), we should be sure an delete any duplicates - thanks thanks!

Yup, I circle back there and delete the items that were published here

@Hareet Hareet merged commit ded5b85 into main Jan 21, 2026
2 checks passed
@Hareet Hareet deleted the add-docs-mcp-server branch January 21, 2026 18:24
@github-project-automation github-project-automation bot moved this from 💻 In Progress to 🚀 Done in CHT Stewardship Activities Q1 2026 Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🚀 Done

Development

Successfully merging this pull request may close these issues.

3 participants