DMoERA Creator

What dMoERA Creator MCP server does

The dMoERA Creator MCP server gives an MCP client access to dMoERA’s crypto trading and fund-management API. Its discovery tools cover supported domains, available strategy data feeds, current market regimes, tracked prices, bot profiles, marketplace listings, and tournament standings. The listed domains include ETH, BTC, and SOL activities such as spot, scalp, crisis, and volatility strategies.

For strategy development, agents can run code through sandbox_backtest, review user strategies, and retrieve strategy report cards. submit_strategy sends a strategy through the platform’s full seven-stage validation process and supports live deployment when the submission qualifies.

The fund features are intended for authenticated users. A user can create a personal hedge fund, add eligible bots, set allocation weights and risk caps, activate or deactivate Manager Mode, and close a fund. Personal funds can contain only the authenticated user’s own bots. Additional reporting tools cover positions, closed trades, performance snapshots, live P&L, analytics, historical tests, and fund report cards.

How it works

The dMoERA Creator MCP server acts as an HTTP API client rather than embedding dMoERA’s internal implementation. An MCP-compatible agent calls the exposed tools, and the server forwards those requests to a running dMoERA backend or the public instance. Clients may run the server locally through a Python command or connect to the documented Streamable HTTP endpoint at https://dmoera.xyz/mcp.

A typical workflow starts with public discovery: inspect domains and features, examine bots, and check market conditions. Strategy code can then be tested in the sandbox over a 60-day window. A more extensive submission uses a 23-month validation window and the platform’s seven validation stages. Fund operations require an API key and can include estimating swap friction before changing a roster.

Setup and configuration

Run the server with Python 3.11 or newer and install the mcp package plus the repository requirements. A local MCP configuration points the client at mcp_creator_server.py using an absolute path.

Set DMOERA_API_URL to the backend address, such as https://dmoera.xyz. DMOERA_API_KEY holds a personal access token created in dMoERA under Settings → API Keys. The key is optional for public discovery and market-data calls, but is required for backtesting, strategy submission, and authenticated user operations. Tokens should not be committed to source control.

Tools and capabilities

• Discover domains, feature feeds, bots, marketplace listings, prices, and market regimes.
• Inspect bot profiles, strategy reports, tournament rounds, and leaderboards.
• Backtest strategy code in an isolated environment and submit it for validation.
• Create, configure, activate, deactivate, and close personal funds.
• Add, remove, or swap eligible bots and update weights or risk caps.
• Review fund positions, trades, P&L, analytics, historical tests, and report cards.

Limitations and notes

The dMoERA Creator MCP server depends on a reachable dMoERA backend. Public discovery tools do not require authentication, while strategy development and fund-management operations generally do. Sandbox backtests use a 60-day period, whereas full strategy submission uses a 23-month window. Historical fund tests are rate limited.

Fund membership is restricted to the authenticated user’s own bots. Removing a bot triggers position wind-down, swapping a bot incurs a friction cost, and permanently closing a fund is irreversible. Activating Manager Mode deploys capital across the configured roster; deactivating it closes positions and returns capital to the wallet.