Skip to main content
Glama
pyalgobot

angelone-mcp

by pyalgobot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to angelone-mcp

No user-submitted related servers found.

    Related Servers

    • Angel One MCP Server

      rohi221b
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage Angel One trading accounts through natural language, including portfolio viewing, order placement and modification, market data retrieval, and advanced trading features.
      MIT

    • zerodha-mcp

      mtwn105
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Zerodha trading accounts, including placing orders, checking portfolio, and viewing positions through MCP integration.
      32
      Apache 2.0

    • icici-mcp

      aranjan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables trading Indian stocks on ICICI Direct through natural conversation with any MCP-compatible AI assistant, featuring automated TOTP login and tools for portfolio monitoring, order placement, and market data.
      MIT

    • Zerodha MCP Server

      anish5256
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language access to Zerodha trading accounts for retrieving portfolio holdings, positions, orders, funds, and real-time market prices. Supports secure authentication for Indian stock market trading operations via Claude, Cursor, and other MCP-compatible AI tools.
      1
      -

    • Zerodha MCP Server

      ManikLakhanpal
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with the Zerodha trading platform for placing stock orders, viewing holdings, and managing mutual fund investments through the MCP protocol.
      4
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools target distinct actions and resources—orders, positions, holdings, GTT rules, market data, and analytics are clearly separated. Minor overlap exists between get_holdings and get_all_holdings, and between get_ltp and get_market_quote, but descriptions clarify their scope.

    Naming Consistency4/5

    The naming mostly follows a clear verb_noun snake_case pattern, such as place_order, cancel_order, get_positions, and search_scrip. The gtt_* tools deviate by leading with the domain prefix instead of the verb, and a few names like get_all_holdings vs get_holdings are slightly inconsistent, but overall the pattern is predictable.

    Tool Count2/5

    With 32 tools, the surface feels heavy and exceeds the 25-tool threshold that typically signals over-expansion. Many market-data and analytics tools could be consolidated or grouped, though the breadth is understandable for a full brokerage API.

    Completeness4/5

    The tool surface covers the core brokerage lifecycle well: authentication, order placement/modification/cancellation, order and trade books, positions, holdings, GTT rules, margin checks, and charge estimation. Some gaps exist such as historical order history or bulk order capabilities, but agents can accomplish most common trading workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources