mcp-meroshare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERO_SHARE_PASSWORD | Yes | Your account password | |
| MERO_SHARE_USERNAME | Yes | Your BOID (username) | |
| MERO_SHARE_CLIENT_ID | Yes | Your DP client ID (e.g., 162) | |
| MERO_SHARE_CRN_NUMBER | Yes | Your CASBA CRN number | |
| MERO_SHARE_TRANSACTION_PIN | Yes | Your transaction PIN (TPIN) |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meroshare_get_dp_listA | List all Depository Participants with their numeric client IDs (call this first to find your client_id) |
| meroshare_loginA | Log in to MeroShare. Password is read from MERO_SHARE_PASSWORD in .env |
| meroshare_logoutA | Log out of MeroShare and clear the session |
| meroshare_get_current_issuesA | List all currently open IPO, FPO, and Rights share issues available for application |
| meroshare_apply_ipoB | Apply for an IPO/FPO/Rights issue. Use dry_run=true to preview without submitting. |
| meroshare_get_application_reportsA | Get all submitted IPO/FPO/Rights application reports |
| meroshare_get_bank_detailsB | Get linked bank account details using your demat number (16-digit) |
| meroshare_get_own_detailA | Get your own account/profile details (name, BOID, demat, email) |
| meroshare_get_transactionsC | Get share transaction history |
| meroshare_check_ipo_resultB | Check IPO/FPO allotment result for a specific issue |
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 10 tools
Each tool has a clearly distinct purpose, from login/logout to applying for IPOs and checking results, with no overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern prefixed with 'meroshare', making them predictable and easy to distinguish.
With 10 tools, the server covers authentication, account details, IPO lifecycle, transactions, and bank info—well-scoped for a stock market application.
Covers core IPO operations and account management well, but lacks a direct tool for viewing current portfolio holdings, though transaction history partially covers it.