nhcx-payer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to true for debug logging to stderr | false |
| NDHM_URL | No | ABDM gateway auth URL | https://dev.abdm.gov.in |
| NHCX_ENV | No | Environment: sandbox, staging, production | sandbox |
| PAYER_ID | No | Your payer code (used as receivercode in API calls) | 1518 |
| MEMBER_ID | No | Default patient ABHA/PMJAY member ID for testing | |
| SENDER_CODE | No | Default provider/sender code for testing | |
| NHCX_RETRIES | No | Auto-retries on transient errors (5xx, network) | 0 |
| NHCX_TIMEOUT | No | API request timeout in milliseconds | 30000 |
| NDHM_CLIENT_ID | Yes | ABDM gateway client ID (sandbox: SBX_000XXX) | |
| NDHM_CLIENT_SECRET | Yes | ABDM gateway client secret | |
| NHCX_USER_ROLE_URL | No | Base URL for get/user-role endpoint | |
| NHCX_PROCESS_CASE_URL | No | Base URL for process/case endpoint |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nhcx_validate_configA | Validate all environment variables and test connectivity to NHCX APIs. Run this first to confirm your setup is correct. |
| nhcx_loginA | Authenticate with the ABDM gateway V3 and cache a session token (15 min). Useful as a connectivity check — all other tools auto-authenticate. |
| nhcx_get_user_roleA | Get the current payer role for a case and the allowed actions for that role. Always call this before processing a case. |
| nhcx_process_caseB | Act as a payer and perform an action on a case: Approve, Reject, Query, Forward, Pending, cpdApprove, cpdReject, iQuery. The usecase is derived automatically from the action. The caseId, action, senderCode, memberId, and correlationId are required. |
| nhcx_workflowA | Show the full payer workflow: steps, usecase per step, roles, and allowed actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: validate config, authenticate, get role/actions, process a case, and view workflow. There is no overlap or ambiguity between them.
Most tools follow a consistent verb_noun pattern (validate_config, get_user_role, process_case), though 'login' and 'workflow' deviate slightly. The nhcx_ prefix is applied uniformly, making the set readable and predictable.
Five tools is well-scoped for a payer-focused MCP server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The set covers configuration, authentication, role discovery, case actions, and workflow understanding. A potential gap is the lack of a tool to explicitly retrieve full case details before processing, but the included tools appear sufficient for the primary payer workflow.