Angel One MCP (Model Context Protocol)

Created By
ankushCodeXa year ago
Local MCP server connecting to Angle One SDK
Overview

What is Angel One MCP?

Angel One MCP (Model Context Protocol) is a local server implementation that connects to the Angel One SDK, allowing users to interact with Angel One's trading APIs to retrieve historical data and portfolio information.

How to use Angel One MCP?

To use Angel One MCP, clone the repository from GitHub, set up a Python virtual environment, install the required dependencies, and configure your API credentials. You can then run the server to interact with the trading APIs.

Key features of Angel One MCP?

  • Local server implementation for Angel One trading APIs
  • Ability to retrieve historical trading data
  • Access to portfolio data through API calls

Use cases of Angel One MCP?

  1. Fetching historical stock prices for analysis.
  2. Monitoring portfolio performance over time.
  3. Integrating trading functionalities into custom applications.

FAQ from Angel One MCP?

  • What are the prerequisites for using Angel One MCP?

You need Python 3.10, an Angel One trading account, and API credentials from Angel One.

  • Is there a graphical user interface for Angel One MCP?

No, Angel One MCP is a command-line tool and does not have a GUI.

  • Can I use Angel One MCP for automated trading?

Yes, you can integrate it with your trading algorithms to automate trading strategies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ankushCodeX
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

11 hours ago