Finvasia MCP Server

What is Finvasia MCP Server?

The Finvasia MCP Server is a Node.js-based server that connects to Finvasia’s Market Connect Protocol (MCP) to enable seamless interaction with the Finvasia trading platform. It acts as a bridge between Finvasia’s API and MCP-based applications, providing a standardized stdio interface for accessing trading account data and executing orders.

How to use Finvasia MCP Server?

Clone the repository, install dependencies with npm install, create a .env file with your Finvasia credentials (ID, PASSWORD, VENDOR_KEY, IMEI, API_KEY, TOTP), run npm run build and then npm start. The server starts on http://localhost:3000. Configure your MCP client by adding an SSE entry in its settings JSON pointing to http://localhost:3000.

Key features of Finvasia MCP Server

• Fetch user profile data
• Fetch account balance
• Place buy and sell orders
• Cancel and modify orders
• Get current stock prices, positions, and holdings
• Retrieve order margin, order book, and trade book
• Place take profit and stop loss orders
• Support for options buy and sell

Use cases of Finvasia MCP Server

• Programmatically placing and managing equity orders from a custom frontend
• Monitoring real-time portfolio positions and holdings
• Automating trading strategies with stop-loss and take-profit orders
• Integrating Finvasia account data into MCP-compatible dashboards and tools

FAQ from Finvasia MCP Server

What runtime does it require?

Node.js is required to run the server.

How do I configure my Finvasia credentials?

Create a .env file in the project root with the keys ID, PASSWORD, VENDOR_KEY, IMEI, API_KEY, and TOTP using your Finvasia account details.

What transport protocol does it use?

The server communicates via SSE (Server-Sent Events) over HTTP on localhost:3000.

Where can I get support?

Contact blaze.ws for assistance, troubleshooting, or feature requests.

Is the server secure for production use?

The README does not provide specific security guidance. It is intended for integration and should be reviewed for production deployment.