Tradememory Protocol MCP Server

The AI trading stack is missing a layer. Every MCP server handles execution — placing orders, fetching prices, reading charts. **None handle memory.**

Remote serverstreamable-httpPython

What is the Tradememory Protocol MCP server?

Most knowledge and memory work still happens through a UI a human drives. Tradememory Protocol MCP server moves it into the conversation instead. The AI trading stack is missing a layer. Every MCP server handles execution — placing orders, fetching prices, reading charts. None handle memory..

The short version

  • Before trading: — ask your memory — what happened last time in this market condition? How did it end?
  • After trading: — one call records everything — five memory layers update automatically
  • Safety rails: — confidence tracking, drawdown alerts, losing streak detection — the system tells you when to stop

The tools it exposes

The server publishes 7 tools. What each one is for:

  • Category — Tools
  • Memory — remember_trade · recall_memories
  • State — get_agent_state · get_behavioral_analysis
  • Planning — create_trading_plan · check_active_plans
  • Risk — check_trade_legitimacy
  • Audit — export_audit_trail · verify_audit_hash
  • Evolution — evolution_fetch_market_data · evolution_discover_patterns · evolution_run_backtest · evolution_evolve_strategy · evolution_get_log

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tradememory Protocol's toolset — Category, Memory, State and 4 more — is a fair guide to whether it matches your workflow. It is maintained by mnemox-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CategoryTools
Memoryremember_trade · recall_memories
Stateget_agent_state · get_behavioral_analysis
Planningcreate_trading_plan · check_active_plans
Riskcheck_trade_legitimacy
Auditexport_audit_trail · verify_audit_hash
Evolutionevolution_fetch_market_data · evolution_discover_patterns · evolution_run_backtest · evolution_evolve_strategy · evolution_get_log

How to install the Tradememory Protocol MCP server

{
  "mcpServers": {
    "tradememory-protocol": {
      "command": "uvx",
      "args": ["tradememory-protocol"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Tradememory Protocol to Category.
  • Use Tradememory Protocol to Memory.
  • Use Tradememory Protocol to State.

Frequently asked questions

It connects Tradememory Protocol to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (Category, Memory, State, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Tradememory Protocol directly.