@belal-elsabbagh-apex/copilot-mcp

MCP server exposing EHR Copilot operations over stdio. Built with Bun (bun build bundles src/ → a node-runnable dist/server.js), so it runs under either bunx or npx. Published as a private package on GitHub Packages.

Tools

Related MCP server: copilot-mcp-server

Configuration

The server reads one validated config holding both the Copilot BE creds and the UiPath args. Two ways to provide it:

1. Single file (preferred): set COPILOT_MCP_CONFIG to a JSON file shaped like config.example.json.

2. Split legacy files: set COPILOT_MCP_LOCAL_DIR to a directory containing order-copy-credentials.json + uipath-config.json (+ optional overrides.json).

The uipath.noteBucket / queueUrl / addQueueItemPath / serverUrlByEnv fields are only required by build_queue_item. overrides (per-prodUid clone remaps) is optional.

Other env vars: COPILOT_MCP_DEBUG_DIR (where clone_order dumps the extracted prod order JSON; defaults to the OS temp dir).

Local development

bun install
bun run typecheck
bun run build        # bundle src -> dist/server.js (node-runnable, what npx/bunx execute)
bun run start        # run from source via bun (no build needed)
bun run dev          # watch mode

Installing from GitHub Packages (private)

The package is private, so installing requires a GitHub token with read:packages.

Add to the consumer repo's .npmrc:

@belal-elsabbagh-apex:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}

Then export NODE_AUTH_TOKEN=<your PAT> and install:

bun add -d @belal-elsabbagh-apex/copilot-mcp

Wire into .mcp.json

{
  "mcpServers": {
    "copilot": {
      "command": "npx",
      "args": ["-y", "@belal-elsabbagh-apex/copilot-mcp"],
      "env": {
        "COPILOT_MCP_CONFIG": "/abs/path/to/config.local.json"
      }
    }
  }
}

npx and bunx are interchangeable here (the published bin, dist/server.js, is a plain node ESM entry). Use COPILOT_MCP_LOCAL_DIR instead of COPILOT_MCP_CONFIG for the split legacy files.

Publishing

Publishing is tag-driven. Bump version in package.json, commit, then push a matching vX.Y.Z tag:

git tag v1.2.0
git push origin v1.2.0

That one tag push fans out to two workflows (both keyed off the tag, because a GITHUB_TOKEN-created release does not trigger other workflows):

• Release on tag (release.yml) — creates a GitHub Release with auto-generated notes.

• Publish (publish.yml) — typechecks, builds, and runs bun publish --access restricted using the repo's GITHUB_TOKEN (packages: write), keeping the package private. Also runnable manually via workflow_dispatch.