Skip to main content
Glama

trackr-mcp

MCP server for the ForexTrackr read-only API. On startup it loads the API's public OpenAPI spec (/api/public/docs.json) and exposes every operation your API key may call as a tool (account lookup, current session, dashboard, executive, operations, payments, retention, sales, management).

Get an API key from a ForexTrackr admin (Admin Settings > User Management > API Keys). Tools outside the key's scopes answer 401.

Install (Claude Code plugin)

Requires Node.js 20+. In Claude Code:

/plugin marketplace add jakuubkoo/trackr-mcp
/plugin install trackr@forextrackr

Claude Code asks for your ForexTrackr address and API key when the plugin is enabled (firm 1, plus an optional firm 2) and keeps the keys in the system keychain (~/.claude/.credentials.json on Linux). Change them later with /plugin configure trackr@forextrackr, then restart Claude Code. Updates: /plugin marketplace update forextrackr.

Related MCP server: stonex-mcp

Several firms

Each firm is a ForexTrackr instance with its own address and key. Ask Claude "which firms do I have?" or "switch to firm2": the switch_firm tool lists the firms and switches every tool to another one; the choice is kept across restarts. More firms than the two in the plugin settings: "log in to firm3 at https://... with trk_..." (the login tool saves it under that name), logout forgets one.

Claude Desktop or without the plugin

Clone the repository and point the client at dist/index.js (no npm install needed):

{
  "mcpServers": {
    "trackr": { "command": "node", "args": ["/path/to/trackr-mcp/dist/index.js"] }
  }
}

Development

npm install, edit index.js, then npm run build and commit dist/index.js with it (the plugin runs the bundle).

Sign in without the plugin

Claude Desktop or a cloned copy: tell Claude "log in to ForexTrackr at https://... with trk_..." once. The login tool checks the key and saves it with the address in ~/.config/trackr-mcp/config.json (readable only by you); logout deletes the key. TRACKR_FIRM1_URL / TRACKR_FIRM1_API_KEY (and FIRM2) environment variables work too; TRACKR_URL / TRACKR_API_KEY set firm1.

Dates are YYYY-MM-DD, and to includes its own day. Some tools are precomputed once a night and answer only the preset ranges their description lists.

The overrides table in index.js corrects the generated tools: it hides misleading or duplicate ones (the *_all concatenations, the 5 MB balances list, leverage distribution), drops ignored parameters, trims large payloads and says in each description whose P&L a figure is (broker or client).

License

MIT

Available Tools

3 tools
loginA

Sign in to a ForexTrackr firm with an API key (trk_..., an admin creates it in Admin Settings > User Management > API Keys). The key and URL are checked and saved on this computer under the firm name, which becomes the active firm.

Inputs: api_key (required), url, firm.

logoutA

Forget the saved API key of a ForexTrackr firm.

Inputs: firm.

switch_firmA

List the ForexTrackr firms set up and which one is active, or switch every tool to another firm. Call it before answering about a firm other than the active one.

Inputs: firm.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a single, clearly distinct session operation: authenticate (login), inspect/change the active firm (switch_firm), and clear credentials (logout). There is no realistic scenario where an agent could confuse these three actions.

    Naming Consistency4/5

    All names are lowercase snake_case and verb-oriented (login, switch_firm, logout), so the pattern is readable and predictable. The only minor deviation is that login/logout are bare verbs while switch_firm uses verb_noun, but the convention is still coherent.

    Tool Count4/5

    Three tools is small, but it is well matched to a narrow session/authentication scope where each tool earns its place. It would be thin only if the server were expected to expose broader ForexTrackr data operations, which the surface does not claim.

    Completeness4/5

    The full credential lifecycle is covered: authenticate, switch between firms (which also reports the active firm, avoiding a separate list tool), and forget credentials. Minor gaps are the absence of a standalone status/whoami check and any key-refresh or multi-key management operation, but agents can work around these via switch_firm.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server exposing StoneX Client REST API endpoints as tools, enabling account balances, positions, activity, and performance retrieval via natural language. Requires a user-supplied access token or session cookie.
      21 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides login-gated access to FindData's crawled business data, enabling users to read indicators over time, list concepts, search via natural language, and run graph queries.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to App Store Connect analytics, sales, finance, and customer review data, with tools to fetch and parse reports from Apple's Analytics Reports API and other report endpoints.
      14
      Apache 2.0