← Projects

Windows trading workstation

LunaBot

A Windows workspace for market charts, orders, strategy review and reporting, with MetaTrader 5 and assistant connections.

My roleDesktop product development and integrations.
Reconstructed LunaBot Windows trading workspace with its dark XAUUSD demo chart, order ticket and a connected assistant context panel.
Portfolio reconstruction · sample dataFull size ↗

Overview

Project overview

  • Account setup
  • Charts and orders
  • Strategy review
  • Reports and connected assistants

Engineering contribution

My contribution

  • Built account setup, chart and order-review workflows.
  • Connected strategy configuration, research and activity reporting.
  • Published Windows releases and illustrated setup guides.

Technology & scope

  • Windows
  • MetaTrader 5
  • MCP / tool calling
  • Account-scoped tools
  • Provider integrations

Technical details

Technical implementation

A Windows workstation that connects market workflows with structured, permission-aware assistant tools.

01

Workstation integration

Account setup, charting, order review, strategy configuration and reporting share the workstation context. MetaTrader integration connects the desktop interface to its trading environment.

02

MCP tools and account grants

A stdio MCP server exposes strictly structured tools. A registry maps requests to engine functions; account-scoped grants and revocation control what a connected assistant may access.

03

Permission and risk checks

Permissions and risk checks remain inside the application. Assistant requests pass through those rules rather than writing directly around them.

Workflow

MCP connection

  1. 01

    Request

    An assistant calls a structured tool.

  2. 02

    Scope

    Account grants limit available actions.

  3. 03

    Check

    The engine enforces permissions and rules.

  4. 04

    Return

    A structured result goes back to the assistant.

Account-scoped grants can be revoked. The application engine remains responsible for enforcing actions.

Verification

Build & verification

My test-driven workflow separates engine behaviour from desktop and broker integration. AI-assisted changes are reviewed against permissions, proposals and recorded outcomes.

Verification examples
MCP access and revocation tests
MCP checks cover account scope, revocation, approval requirements and duplicate requests. The application engine still enforces the action.
Order lifecycle checks
Paper workflows exercise proposal, approval, confirmation, closure and reporting. Real terminal and broker behaviour requires a separate integration check.
Next projectOngea na Waziri wa Afya