DhanHQ MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHAN_CLIENT_ID | Yes | Your DhanHQ Client ID | |
| DHAN_ACCESS_TOKEN | Yes | Your DhanHQ Access Token |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_holdings_summaryB | Fetch holdings summary via DhanHQ SDK. |
| get_all_ordersA | Fetch all orders from DhanHQ account. Returns a list of all orders with their details including order ID, status, quantity, price, etc. |
| get_trade_historyA | Fetch trade history within a date range. Parameters:
Returns all trades executed within the specified date range with details including: trade ID, order ID, quantity, price, time, and settlement status. |
| renew_access_tokenA | Renew the DhanHQ access token for another 24 hours. This expires the current token and provides a new token with 24 hours validity. Note: Only works with tokens generated from Dhan Web (web.dhan.co). Returns the new access token that should be updated in your environment variables. |
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 4 tools
Each tool has a distinct purpose: holdings summary, order list, trade history, and token renewal. There is no overlap or ambiguity between them.
All tool names follow a clear verb_noun pattern: get_holdings_summary, get_all_orders, get_trade_history, and renew_access_token all use a consistent style. The slight verb variation is appropriate for different actions.
Four tools is well within the ideal range and the scope is tightly focused on retrieval plus one maintenance operation. No unnecessary bloat.
The core read operations are covered (summaries, orders, trades) plus token renewal, but missing functionality like account balance or positions could be expected. Still, the surface is reasonably complete for a read-only-style server.