# Local Knowledge MCP Servers for OpenEMR on ECS and EKS

**URL:** <https://community.open-emr.org/t/local-knowledge-mcp-servers-for-openemr-on-ecs-and-eks/26975>\
**Category:** OpenEMR Development\
**Created:** [August 16, 2026, 2:05pm UTC](https://community.open-emr.org/t/local-knowledge-mcp-servers-for-openemr-on-ecs-and-eks/26975 "2026-08-16T14:05:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jacob\_Mevorach](https://community.open-emr.org/user_avatar/community.open-emr.org/jacob_mevorach/32/22319_2.png) [@Jacob\_Mevorach](https://community.open-emr.org/u/Jacob_Mevorach)\
**Post date:** [August 16, 2026, 2:05pm UTC](https://community.open-emr.org/t/local-knowledge-mcp-servers-for-openemr-on-ecs-and-eks/26975/1 "2026-08-16T14:05:26Z")

</div>

Hello all!

Wanted to share that read only knowledge [MCP servers](https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro) were recently added to both [OpenEMR on ECS](https://github.com/openemr/openemr-on-ecs) and [OpenEMR on EKS](https://github.com/openemr/openemr-on-eks).

Both of these projects aim to be production-grade, highly managed AWS installations that can scale to massive size while still being relatively affordable and easy to manage. They are also both MIT-0 licensed and can be modified or used as is for free or commercial use without any need to attribute anything to the original authors. ([OpenEMR on ECS License](https://github.com/openemr/openemr-on-ecs/blob/main/LICENSE), [OpenEMR on EKS License](https://github.com/openemr/openemr-on-eks/blob/main/LICENSE))

They also contain a lot of tooling which can be overwhelming and disorienting to new users and/or contributors. Especially for people who may be new to [CDK](https://github.com/aws/aws-cdk), [Terraform](https://github.com/hashicorp/terraform)/[OpenTofu](https://opentofu.org/), [ECS](https://aws.amazon.com/pm/ecs/) or [Kubernetes](https://kubernetes.io/).

These knowledge only MCPs run locally for free on your own machine and provide the ability to MCP capable clients (i.e. [Cursor](https://cursor.com/), [Claude Code](https://code.claude.com/docs/en/overview), [Kiro](https://kiro.dev/), [OpenCode](https://opencode.ai/), [Deepseek Harness](https://deepseek.com/harness/en/), etc. etc.) to answer questions or alter code as if they had the knowledge of an experienced maintainer. Hopefully this helps make it meaningfully easier for new users and maintainers who are using MCP capable clients to begin to adopt the project.

**OpenEMR on ECS:**

> **[GitHub - openemr/openemr-on-ecs](https://github.com/openemr/openemr-on-ecs)**
>
> Contribute to openemr/openemr-on-ecs development by creating an account on GitHub.

See `KNOWLEDGE-MCP.md`

**OpenEMR on EKS:**

> **[GitHub - openemr/openemr-on-eks: Democratizing healthcare technology by making...](https://github.com/openemr/openemr-on-eks)**
>
> Democratizing healthcare technology by making enterprise-grade OpenEMR deployments accessible to organizations of any size through automated, cloud-native infrastructure.

See [`docs/KNOWLEDGE_MCP.md`](https://github.com/openemr/openemr-on-eks/blob/main/docs/KNOWLEDGE_MCP.md)
