-
Notifications
You must be signed in to change notification settings - Fork 0
MCP Server
Current status: scaffold only, not yet functional.
mcp-server/ exists in the repository as a Go module:
mcp-server/
├── go.mod # module kinetirx/mcp-server, go 1.26.6
└── go.sum
go.mod declares a dependency on
github.com/modelcontextprotocol/go-sdk
(v1.7.0), which confirms the intent: a Go Model Context Protocol
server that would expose KinetiRx pharmacy operations (inventory lookups,
POS sales, patient/due-khata queries, etc.) as MCP tools, so an AI assistant
(e.g. Claude) could connect to a live KinetiRx instance and act on real
data through the same permission-gated REST API described in
API Reference.
As of this writing there is no server source code, no README, and no
cmd/ entrypoint in mcp-server/ — only the module manifest and its
dependency lock file. There is nothing to run yet.
- How to build and run the MCP server binary (likely
go run ./cmd/...once acmd/package exists, mirroringbackend/cmd/server). - Configuration: presumably a KinetiRx backend base URL and an employee credential or service token, given every KinetiRx API route (other than health/login) is JWT- and permission-gated — an MCP server acting on a user's behalf would need to authenticate the same way any other API client does (see the Architecture auth model section).
- The tool catalog it exposes (e.g. "look up medicine stock," "record a sale," "check a patient's due balance") once those tools actually exist in code.
- How to point a Claude Desktop / Claude Code MCP client config at it.
Don't rely on any tool list or usage instructions for this component from
outside this repository — nothing has been implemented past the module
scaffold, so any such instructions would be speculative. Check
mcp-server/ directly, or this page's edit history, for the current state.