Skip to main content
Glama
fidelity-mcp

fidelity-mcp

by jiaweitang22

Related Servers

Alternatives to fidelity-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Fidelity Investments brokerage accounts using Playwright browser automation to manage balances, positions, and trades. It supports secure 2FA authentication and session persistence for seamless account management via Claude.
      13
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read balances, positions, and transaction history, and place limit sell orders on Fidelity Investments accounts via Playwright browser automation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables browser automation and web interaction control through Playwright, allowing Claude Code to navigate, click, fill forms, take screenshots, and manage sessions.
      73 npm
      9
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Robinhood brokerage accounts via browser automation, supporting portfolio viewing, quotes, trading, and account management.
      8
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a Tastytrade brokerage account to read balances, positions, option chains, screeners and realized P&L, and to preview and place multi-leg orders only after a broker dry-run, an operator live-trading switch and an explicit per-order confirmation in chat.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language browser automation through Claude, wrapping Playwright to execute commands like navigation, clicking, form filling, and screenshots.
      3 npm
      30
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct actions: status/login/logout cover auth, get_accounts vs get_positions vs get_quote cover data, and screenshot vs page_content are split for debugging. The order trio (place_order dry-run, stage_order user-confirmed, batch_orders multi-order) is the main risk; descriptions clarify the boundaries but an agent could still hesitate between place_order and batch_orders for a single account.

    Naming Consistency4/5

    All tools use a consistent fidelity_ prefix and snake_case, with verb_noun patterns like get_positions, place_order, stage_order, batch_orders. The one deviation is fidelity_status, a bare noun rather than a verb phrase, but it stays readable and predictable.

    Tool Count5/5

    Twelve tools is well-scoped for a brokerage automation server, with each tool covering a distinct stage: auth, read, trade, transfer, and debugging. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the full lifecycle: session status, login/logout, accounts, positions, quotes, order placement (dry-run, staged, batch), transfers, and selector debugging. Gaps are minor but real: no order status/cancel or order history, and no transaction history, which an agent may need after placing or staging an order.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues