eToro MCP Server
OfficialDemonstrated as a method to interact with the MCP server's REST API for executing tools like fetching eToro portfolios.
Provides package management for installing dependencies and running scripts for the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eToro MCP Server fetch portfolio for user yoniasia"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
eToro MCP Server
This server provides MCP (Model Context Protocol) tools for interacting with eToro's public API endpoints. It allows you to:
Fetch a user's portfolio using their username
Look up instrument details by IDs
Search for instruments by name prefix (autocomplete)
Getting Started
Install dependencies:
npm installStart the development server:
npm run devBuild for production:
npm run buildStart the production server:
npm start
Related MCP server: IB MCP Server
Available Tools
fetch_etoro_portfolio
Fetches an eToro user's portfolio using their username. The tool automatically converts the username to a Customer ID (CID) internally.
Parameters:
username: The eToro usernameauthToken(optional): Authorization token for authenticated requests
fetch_instrument_details
Fetches details for a list of eToro instruments.
Parameters:
instrumentIds: List of instrument IDs to fetch details forfields(optional): Fields to include in the response (defaults todisplayname,threeMonthPriceChange,oneYearPriceChange,lastYearPriceChange)
search_instruments
Searches for eToro instruments by name prefix (autocomplete).
Parameters:
namePrefix: The prefix to search for in instrument namesfields(optional): Fields to include in the response (defaults tointernalInstrumentId,displayname,internalClosingPrice)
CORS Limitations
Note that some of the eToro API endpoints have CORS restrictions and should be called from a server-side environment. The tools in this server handle these requests on the server side to avoid CORS issues.
Usage Example
The server exposes a REST API for accessing these tools, which can be called from any HTTP client:
GET /tools # List all available tools
GET /tools/:name/schema # Get tool schema
POST /tools/:name/execute # Execute a toolExample of using the fetch_etoro_portfolio tool:
curl -X POST http://localhost:3000/tools/fetch_etoro_portfolio/execute \
-H "Content-Type: application/json" \
-d '{"username": "yoniasia"}'Available Tools
3 toolsfetch_etoro_portfolioB
Fetch an eToro user's portfolio using their username
Inputs: no named parameters.
fetch_instrument_detailsB
Fetch details for a list of eToro instruments
Inputs: no named parameters.
search_instrumentsB
Search for eToro instruments by name prefix (autocomplete)
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: fetch_etoro_portfolio retrieves user portfolio data, fetch_instrument_details gets details for specific instruments, and search_instruments performs autocomplete searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with snake_case: fetch_etoro_portfolio, fetch_instrument_details, and search_instruments. The naming is predictable and readable throughout the set.
With only 3 tools, the server feels thin for a financial trading domain like eToro. While the tools cover basic fetching and searching, the scope suggests more operations (e.g., trading actions, account management) would be expected, making the count borderline low.
The toolset is significantly incomplete for an eToro server. It lacks core operations such as placing trades, managing orders, viewing account details, or accessing market data beyond instruments. This creates gaps that will likely cause agent failures in real-world trading scenarios.
Related MCP Connectors
Trade and invest in tokenized stocks: prices, holdings, P&L, unsigned market/limit/recurring trades.
Broad, OAuth-protected provider and financial-domain API tools for research agents.
Read-only stock research; OAuth unlocks your own portfolio, watchlist, and Smart Alerts.
Market data, accounts, portfolio and orders via the EXANTE HTTP API.
Related MCP Servers
- FlicenseBqualityDmaintenanceProvides tools to get financial data (stock prices, company information) and generate financial visualizations through the Model Context Protocol.1011-
- FlicenseNot gradedqualityAmaintenanceEnables interaction with Interactive Brokers through the official IBKR Web API, providing access to account management, brokerage sessions, and trading endpoints via the Model Context Protocol.-
- FlicenseNot gradedqualityAmaintenanceEnables programmatic access to Tiingo financial data—stock prices, news, forex, fundamentals, and corporate actions—through the Model Context Protocol.-
- FlicenseNot gradedqualityAmaintenanceEnables interaction with Interactive Brokers' Web API through the Model Context Protocol, including brokerage session setup, authentication, and protected endpoint access for account and trading workflows.-