home / mcp / health id service mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-health-id-service": {
"url": "https://api.apis.guru/v2/specs/ndhm.gov.in/ndhm-healthid/1.0/openapi.json",
"headers": {
"CONFIG": "{ ... }",
"SECURITY": "YOUR_API_KEY",
"CONFIG_PATH": "/path/to/mcp_config.json"
}
}
}
}You run an MCP (Model Context Protocol) server to expose a defined API in a standardized way so clients can interact with your data model through consistent RPC-like calls. This guide shows how to run the Health ID MCP server and how to connect a client to it, using both remote HTTP access and a local stdio startup flow.
You can access the Health ID MCP server in two primary ways. First, connect via HTTP to a remote MCP endpoint that exposes the Health ID OpenAPI surface, allowing you to send requests over the network. Second, run the local stdio MCP server on your machine to interact with it directly from your development environment.
Prerequisites you need before starting:
Step by step to run the server using the HTTP endpoint and the local stdio mode:
Use these two explicit MCP connection methods. The HTTP method uses a remote MCP endpoint described by its OpenAPI surface, and the stdio method runs the server locally via a Python script.
{
"mcpServers": {
"healthid_openapi": {
"type": "http",
"name": "healthid_openapi",
"url": "https://api.apis.guru/v2/specs/ndhm.gov.in/ndhm-healthid/1.0/openapi.json",
"args": []
},
"healthid_stdio": {
"type": "stdio",
"name": "healthid_stdio",
"command": "python",
"args": ["mcp_server/main.py", "stdio"],
"env": [
{"name": "CONFIG_PATH", "value": "path/to/mcp_config.json"},
{"name": "CONFIG", "value": "{...json config...}"},
{"name": "SECURITY", "value": "API_KEYS or other security params"}
]
}
}
}