Skip to main content
Glama
Sparker0i

Indian Broker MCP Server

by Sparker0i

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNodebug, info, warn, or errorinfo
RECORDINGS_DIRNoOutput directory for learn_broker_navigation./recordings
BROWSER_SLOW_MONoDelay in ms between Playwright actions100
BROWSER_DATA_DIRNoPersistent browser profile storage./browser-data
BROWSER_HEADLESSNoSet true to run browsers headless (login still needs headed mode)false
SESSION_TTL_HOURSNoSession expiry time in hours6
SESSION_ENCRYPTION_KEYNo32-byte hex key for AES-256-GCM session encryptionAuto-generated

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
broker_statusA

Show connection status for all brokers

broker_connectC

Connect to an Indian broker by opening a browser for login

broker_disconnectA

Disconnect from a broker and wipe session data

get_holdingsC

Fetch stock holdings from connected brokers

get_positionsC

Fetch open positions from connected brokers

get_ordersB

Fetch today's order history from connected brokers

get_mutual_fundsB

Fetch mutual fund holdings from connected brokers

get_us_stocksB

Fetch US stock holdings from connected brokers

get_goldA

Fetch gold holdings from connected brokers

get_fno_positionsC

Fetch F&O positions from connected brokers

get_portfolio_summaryB

Aggregated portfolio summary across all connected brokers

search_stockB

Search for a stock or mutual fund by name or symbol

get_quoteC

Get current price quote for a stock

learn_broker_navigationC

Open a browser to record navigation patterns, XHR requests, and DOM snapshots for a broker

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
broker_status_resourceCurrent connection status for all brokers
portfolio_summary_resourceAggregated portfolio summary across all connected brokers

TDQS

B3.2/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but get_positions and get_fno_positions could be confused since F&O positions are a subset of positions. Similarly, get_holdings, get_mutual_funds, get_us_stocks, and get_gold are differentiated by asset type, which is clear. Overall, the tools are separable by their descriptions.

Naming Consistency3/5

The naming convention is mixed: some tools follow a verb_noun pattern (e.g., get_holdings, search_stock), while others use a noun_verb pattern (e.g., broker_connect, broker_disconnect). This inconsistency is not chaotic but could be more uniform. Both patterns use lowercase with underscores, so it's readable.

Tool Count5/5

14 tools is appropriate for a broker aggregation server. The count is well within the typical 3-15 range, and each tool addresses a specific aspect of broker connectivity, data retrieval, or usability. None feel redundant.

Completeness3/5

The tool set covers connection management, holdings, positions, and orders, but misses obvious financial data like cash balances and trade history. It also lacks any trading or order placement capabilities, which could be expected for a broker MCP, though it may be intentionally read-only. The core read-only aggregation surface is present, but notable gaps exist.

Maintenance

ActivityInactive
ResponsivenessNo issues