etrink-mcp
Official# etrink-mcp
MCP server for [etrink](https://etrink.com): cloud MetaTrader 5 accounts and 24/7 bot hosting, driven by
Claude, OpenAI Codex, Gemini CLI, Cursor or any other MCP client. stdio transport, Node.js 18+, no runtime
dependencies (the published file is a single bundle).
This repository is the server implementation: TypeScript sources in [`src/`](src/) (`index.ts` — MT5 tools,
`services-tools.ts` — service hosting tools, `apiClient.ts` — HTTPS client for `api.etrink.com`), built with
esbuild into `dist/etrink-mcp.mjs`. Published on npm as [`etrink-mcp`](https://www.npmjs.com/package/etrink-mcp).
## Run
```bash
ETRINK_API_KEY=etrk_mcp_... npx -y etrink-mcp
```
Create the API key at https://etrink.com/app/api-keys (the key is shown once — keep it in an env var or a
`.env` file and point `ETRINK_ENV_FILE` at it; never commit it).
| Env | Meaning |
|---|---|
| `ETRINK_API_KEY` | Your etrink API key (required) |
| `ETRINK_ENV_FILE` | Path to a `.env` file that contains `ETRINK_API_KEY=...` (alternative to the above) |
| `ETRINK_API_BASE` | API base URL, default `https://api.etrink.com` |
Client config (Claude Desktop, Cursor, Gemini CLI, … — `mcpServers` JSON):
```json
{ "mcpServers": { "etrink": { "command": "npx", "args": ["-y", "etrink-mcp"],
"env": { "ETRINK_ENV_FILE": "/full/path/.env" } } } }
```
Claude Code: `claude mcp add etrink -e ETRINK_ENV_FILE=/full/path/.env -- npx -y etrink-mcp`
## Tools
- MT5 (read): `list_accounts`, `get_open_positions`, `get_positions`, `get_report`, `get_trades`, `get_recent_signals`
- MT5 (write — the agent must dry-run with `test: true` and get the user's confirmation): `place_order`, `open_account`
- Service hosting: `list_services`, `get_service`, `create_service`, `deploy_service`, `get_build`, `list_releases`,
`get_service_logs`, `set_service_env`, `update_service`, `start_service`, `stop_service`, `restart_service`,
`rollback_service`, `exec_in_service`, `delete_service`
Every order passes the same server-side guards as etrink webhooks (plan limits, symbol allow-list, volume
cap, idempotency). How an agent should use the tools safely: the companion Agent Skill
[etrinkhq/etrink-skill](https://github.com/etrinkhq/etrink-skill) (Claude, Codex, Gemini CLI, Cursor).
## Build
```bash
npm install && npm run build # → dist/etrink-mcp.mjs
```
License: MIT
TDQS
Scored across 23 tools
Most tools map to a distinct resource+action: service lifecycle (create/deploy/start/stop/restart/rollback/delete), observability (get_service, get_build, get_service_logs, list_releases), and MT5 trading (accounts, positions, orders, signals, reports, trades). The one real collision is get_positions (single account, live) versus get_open_positions (all accounts, last snapshot), which return near-identical data and invite misselection; get_recent_signals vs get_trades vs get_report are close but descriptions differentiate them (events vs closed trades vs aggregate).
All 23 names are snake_case with a leading verb (list_/get_/create_/delete_/update_/start_/stop_/restart_/deploy_/rollback_/set_/exec_in_), which is highly predictable. Minor deviations: get_build and list_releases omit the '_service'/'service_' qualifier that the other ~15 hosting tools use, making them look domain-agnostic even though they are service-scoped.
23 tools is heavy for a single server, and the surface is really two products stapled together (~15 hosting tools plus ~8 MT5 trading tools). Each half is reasonably scoped on its own, but the combined set exceeds the comfortable 3-15 range and increases selection cost.
Hosting coverage is essentially complete: create, deploy, build status, releases, logs, env, start/stop/restart, rollback, update, delete, plus one-off exec — no dead ends. Trading coverage handles accounts, positions, order placement/close, signals, trades and reporting, but lacks account-level operations (update/delete account, balance/deposit history) and richer order management (modify SL/TP, pending orders).