National Health Authority MCP Server Integration Guide
Section A: Quick Answer & Architectural Summary
The National Health Authority Model Context Protocol (MCP) integration bridges AI coding assistants to the National Health Authority security API. It exposes 1 validated endpoint operations as callable tools for Claude Desktop, Cursor, and VS Code. Configuration is managed via hosted registry at /config/apisetu-gov-in-pmjay.json or local stdio bridge execution. Operates with zero authentication credentials out of the box. Contains 1 mutating operations (POST/PUT/DELETE); user confirmation is recommended before triggering write operations.
MCPBridge Editorial Verdict: National Health Authority
AI coding workflows requiring programmatic access to National Health Authority (Security) endpoints
Low (1-2 mins)
Zero Authentication Required
Automated Spec Tracking
Claude Desktop, Cursor IDE, VS Code (Cline), Zed Editor
Read & Mutating endpoints; client confirmation and least-privilege token recommended
MCPBridge rates National Health Authority as a standardized OpenAPI-to-MCP bridge providing structured tool definitions across 1 endpoints.
Technical Overview & Protocol Integration
The National Health Authority API for PM-JAY e-card management represents a critical digital public infrastructure endpoint, enabling programmatic access to the Ayushman Bharat Pradhan Mantri Jan Arogya Yojana (PM-JAY) health benefit scheme. Provided by the National Health Authority (NHA) of India, this API's core capability is to facilitate the issuance and retrieval of PM-JAY e-cards, which serve as digital proof of eligibility for cashless and paperless treatment at empaneled hospitals. The specific POST /pmjay/certificate endpoint is designed for authorized entities—such as hospital administrators, third-party aggregators, and government portals—to trigger the generation and delivery of a beneficiary's e-card to their integrated DigiLocker account. This moves beyond a simple consumer-facing document view, enabling enterprise use cases like automated beneficiary onboarding for hospital networks, real-time eligibility verification during hospital admission workflows, and the secure, auditable distribution of health insurance credentials across partner ecosystems.
Exposing this API as a tool via the Model Context Protocol (MCP) unlocks powerful, context-aware automation for AI coding assistants and intelligent agents. Within an MCP server configuration, the tool would translate natural language instructions into precise API calls, allowing the AI to operate as a direct bridge between human intent and national health system transactions. Its value lies in its specificity and its connection to a live, government-managed beneficiary database. An AI agent becomes a capable co-developer for health-tech applications, able to instantly test and integrate e-card issuance flows, simulate beneficiary onboarding journeys, or debug integration issues by dynamically generating test certificates in a sandbox environment. This drastically reduces context-switching and manual API testing, accelerating development cycles for solutions that rely on verified PM-JAY status.
Practical workflows enabled by this MCP tool are numerous. A developer could instruct the AI to "Query the NHA API to issue a test PM-JAY e-card for beneficiary ID 123 and send it to my test DigiLocker instance to validate our app's document-fetching logic." The AI would structure the POST request, handle the payload, and report the outcome. Another dynamic task would be: "Generate a batch of mock PM-JAY certificates for 10 different beneficiary IDs to populate our QA database and stress-test our eligibility dashboard." Furthermore, the tool could be used for integration verification: "Using the MCP server, attempt to issue a certificate for a known active beneficiary and confirm the JSON response matches our expected schema, flagging any discrepancies." These examples demonstrate how the AI moves beyond code completion to perform system-aware validation and data provisioning tasks.
Given the current "None" authentication method, which is highly unusual and suggests the endpoint might be in a restricted or sandbox state for specific partners, developers must exercise extreme caution. For any production or public-facing integration, implementing robust authentication is non-negotiable. The foremost security best practice is to treat the API as requiring high-privilege access and immediately engage with the NHA's technical partnership channels to obtain proper API keys or OAuth 2.0 credentials. The principle of least privilege must be applied rigorously; any service account used should have permissions scoped exclusively to the certificate issuance endpoint, with no broader system access. Developers configuring the MCP server should store any obtained credentials in a secure secrets manager, never in code or configuration files. All API calls should be logged and monitored for anomalies, and the use of IP allowlisting, if supported by the NHA, should be enforced to restrict access to trusted application servers. This proactive security stance is critical when interacting with an API that handles sensitive national health beneficiary data.
By translating the OpenAPI 3.0 specification for National Health Authority into native Model Context Protocol (MCP) tool definitions, developers and AI agents gain programmatic access to endpoints over stdio or HTTP transports. Every endpoint is translated into a discrete tool payload complete with input argument validation, parameter descriptions, and return type definitions.
2. Technical Specifications Matrix
System Specifications
| API Name | National Health Authority |
| Slug Identifier | apisetu-gov-in-pmjay |
| Category | Security |
| Auth Method | None Required |
| Endpoint Count | 1 tools mapped |
| Spec Version | OpenAPI v3.0.0 |
| Transport Type | STDIO |
| Publisher Source | auto |
Developer Resources
3. Multi-Client Installation Matrix
Copy and paste these pre-formatted JSON snippets into your MCP client configuration files.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"apisetu-gov-in-pmjay": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apisetu.gov.in/pmjay/3.0.0/openapi.json"
],
"env": {
"NATIONAL_HEALTH_AUTHORITY_API_KEY": "your_national_health_authority_api_key"
}
}
}
}Cursor IDE
Settings → MCP Servers → Add Hosted Config
{
"mcpServers": {
"apisetu-gov-in-pmjay": {
"url": "https://mcpbridge.org/config/apisetu-gov-in-pmjay.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline
Use with MCP extension config
{
"mcpServers": {
"apisetu-gov-in-pmjay": {
"url": "https://mcpbridge.org/config/apisetu-gov-in-pmjay.json"
}
}
}4. Security Architecture & Credentials Reference
Key parameters and credential variable mappings for National Health Authority.
Security Considerations & Sandbox Guidance: National Health Authority
Authorization credential isolation, least privilege boundaries, and container sandboxing options.
None Required
Read & Mutating Operations
Local MCP bridge process making outbound HTTPS requests to upstream API
Isolation & Principle of Least Privilege
Ensure outbound network access to the API endpoint is permitted. Use restricted API tokens with minimal read/write scopes.
Actionable Operational Guidelines
- Verify network firewall rules allow outbound traffic to upstream API endpoints.
- Review arguments for mutating endpoints (/pmjay/certificate) before execution.
- Apply token rate limits and monitor usage in your provider dashboard to prevent unexpected quota consumption.
| Variable Name | Required | Example Value |
|---|---|---|
| NATIONAL_HEALTH_AUTHORITY_API_KEY | REQUIRED | your_national_health_authority_api_key |
5. Endpoints & Tool Schemas Matrix
Search and inspect the 1 tool signatures mapped from OpenAPI.
Executable Code Integration Examples
Call National Health Authority endpoints via cURL, TypeScript, or Python REST SDKs.
curl -X POST "https://api.apis.guru/v2/specs/apisetu.gov.in/pmjay/3.0.0/pmjay/certificate" \ -H "Content-Type: application/json" \ # No auth required
Concrete Real-World Use Cases for National Health Authority
Practical multi-step agentic workflows and prompt directives demonstrating concrete developer outcomes.
Automated Contextual Workflow Integration
Practical workflows enabled by this MCP tool are numerous. A developer could instruct the AI to "Query the NHA API to issue a test PM-JAY e-card for beneficiary ID 123 and send it to my test DigiLocker instance to validate our app's document-fetching logic." The AI would structure the POST request, handle the payload, and report the outcome. Another dynamic task would be: "Generate a batch of mock PM-JAY certificates for 10 different beneficiary IDs to populate our QA database and stress-test our eligibility dashboard." Furthermore, the tool could be used for integration verification: "Using the MCP server, attempt to issue a certificate for a known active beneficiary and confirm the JSON response matches our expected schema, flagging any discrepancies." These examples demonstrate how the AI moves beyond code completion to perform system-aware validation and data provisioning tasks.
- AI assistant inspects prompt context and selects relevant tool
- Validates parameter payload against OpenAPI JSON Schema
- Executes tool call and formats structured API response
Automated Mutation & Resource Creation
Execute state changes and create records through POST operations like "/pmjay/certificate" with parameter validation.
- Agent constructs validated request body matching schema
- Prompts user for execution confirmation
- Executes tool and confirms response status
Good Fit vs. Poor Fit Criteria for National Health Authority
Architectural guidelines to determine when to adopt this integration and when to explore alternatives.
When to Choose / Good Fit
- AI coding assistants in Claude Desktop or Cursor requiring structured tool access to National Health Authority.
- Developers who want standardized OpenAPI-to-MCP translation without building custom server code.
- Workflows that benefit from automated parameter validation against official OpenAPI 3.0 schemas.
- Teams seeking zero-maintenance hosted JSON configurations for easy distribution.
When to Avoid / Poor Fit
- Ultra-high frequency data ingestion exceeding typical LLM context windows and token rate limits.
- Unattended autonomous agent loops with write access where human approval of mutations is mandatory.
- Environments lacking outbound internet access to upstream National Health Authority API servers.
Verification & Evidence Audit: National Health Authority
OpenAPI 3.0 specification parsed and validated via automated build pipeline.
Independent Evidence Checks
Valid specification version 3.0.0 with 1 endpoints indexed.
No authentication required.
JSON Schemas mapped to MCP tools/call standard format.
Automated schema validation only; live upstream API calls require developer credentials.
Project Health & Maintenance Audit: National Health Authority
ActiveActivity & Cadence
Transparent Quality Score Breakdown
Alternatives & Comparison Table (Security)
Comparative trade-offs between National Health Authority and similar ecosystem tools in the Security category.
| Option | Best For | Main Difference vs. National Health Authority | Setup / Runtime | Explore |
|---|---|---|---|---|
| 1Password Connect | Developers needing Security operations with 10 tools | 10 endpoints vs 1 endpoints | auto / v1.5.7 | View → |
| Adyen Balance Control API | Developers needing Security operations with 1 tools | 1 endpoints vs 1 endpoints | auto / v1 | View → |
| Agricultural Scientists Recruitment Board | Developers needing Security operations with 1 tools | 1 endpoints vs 1 endpoints | auto / v3.0.0 | View → |
9. Error Resolution & Troubleshooting Guide
Contextual diagnostics for HTTP status codes and JSON-RPC tool bridge operations.
-32600 (Invalid Request)Root Cause: Malformed JSON-RPC payload sent to local MCP bridge process.
Resolution Action: Verify MCP client payload adheres to JSON-RPC 2.0 specification.
-32601 (Method Not Found)Root Cause: Requested operation does not exist in mapped National Health Authority OpenAPI endpoint schemas.
Resolution Action: Inspect Section 5 endpoints table to confirm valid method names and paths.
-32602 (Invalid Params)Root Cause: Missing or invalid parameters for target tool operation.
Resolution Action: Check parameter data types against OpenAPI JSON Schema specification.
429 Rate Limit ExceededRoot Cause: Upstream National Health Authority API request rate limit quota reached.
Resolution Action: Implement exponential backoff in tool execution loop or verify provider plan quotas.
OPENAPI_GATEWAY_TIMEOUTRoot Cause: Upstream National Health Authority endpoint response latency exceeded timeout threshold.
Resolution Action: Verify network connectivity and check provider system status dashboard.
Official Verified Sources for National Health Authority
Authoritative upstream repositories, specifications, package registries, and configuration endpoints.
OpenAPI 3.0 Specification
Machine-readable OpenAPI schema source used for MCP tool mapping.
https://api.apis.guru/v2/specs/apisetu.gov.in/pmjay/3.0.0/openapi.jsonHosted MCPBridge Configuration
Pre-generated Model Context Protocol JSON configuration hosted on MCPBridge.
https://mcpbridge.org/config/apisetu-gov-in-pmjay.jsonOpenAPI-to-MCP Converter Tool
Client-side browser converter to customize or filter endpoint tools.
https://mcpbridge.org/convert/Claim & Maintainer Verification
Submit a claim to verify API publisher ownership and update metadata.
https://github.com/stormlive-ai/mcp-bridge-docs/issues/new?title=Claim+Listing%3A+National+Health+Authority+%28api%3A+apisetu-gov-in-pmjay%29&labels=claim-listing&body=%23%23+Claim+Listing+Request%0A%0AI+would+like+to+claim+this+listing%3A%0A%0A-+**Type%3A**+api%0A-+**ID%3A**+apisetu-gov-in-pmjay%0A-+**Name%3A**+National+Health+Authority%0A%0A%23%23%23+Your+Information%0A%0A**GitHub+Handle%3A**+%3C%21--+your+GitHub+username+--%3E%0A%0A**Email%3A**+%3C%21--+optional%2C+for+verification+--%3E%0A%0A**Relationship+to+this+API%3A**%0A-+%5B+%5D+I+am+the+API+provider+%2F+maintainer%0A-+%5B+%5D+I+am+an+authorized+representative%0A-+%5B+%5D+Other%3A%0A%0A%23%23%23+Verification+Method%0A-+%5B+%5D+I+will+add+a+CNAME%2FTXT+record+to+verify+domain+ownership%0A-+%5B+%5D+I+can+confirm+from+an+email+address+at+the+provider+domain%0A-+%5B+%5D+I+maintain+the+GitHub+repository%0A%0A%23%23%23+Updates+I%27d+Like+to+Make+%28optional%29%0A%3C%21--+What+would+you+like+to+update%3F+Description%2C+links%2C+category%2C+etc.+--%3E%0A%0A---%0A*Submitted+via+MCP-Bridge+claim+form*Frequently Asked Technical Questions: National Health Authority
Targeted developer questions regarding installation, client configuration, credentials, and error resolution.
The National Health Authority MCP server connects AI coding assistants (Claude Desktop, Cursor, VS Code, Zed) to the National Health Authority API using the Model Context Protocol. It converts 1 OpenAPI operations into native MCP tools callable during chat sessions.