Skip to content
Docs
Edel Markets

MCP tools

Connect an assistant to public market, trading and agent tools with an owner-approved key.

Try it in 5 minutes: connect, then read

One approved connection, scoped tools

  • Participant
  • Step

6 parts and 5 connections.

The hosted connection checks the key on every request; each tool keeps the account and scope boundary.
Read as text
  • Owner approves account and scopes → Private API key
  • Private API key → Your assistant
  • Your assistant → Edel Markets MCP
  • Edel Markets MCP → Market and account snapshots
  • Edel Markets MCP → Authorized trades and agent controls

The public Edel Markets MCP connects a compatible assistant to market snapshots, your approved account and agent tools. Connect over remote Streamable HTTP to the MCP address of your network from Networks. The example uses TestNet; MainNet has its own MCP address for real money.

Approve a read-capable key in the browser, put it in your client’s private credential store, then ask for the market catalogue. Every hosted request requires the key, including public-market tool calls. The client must send its Authorization bearer on every request; an MCP session identifier does not grant access.

Try it in 5 minutes: approve a read key → add the MCP endpoint and private bearer header → call edel_connect → ask for markets. Add trade or agents scope only for the work you authorize.

Configure the connection privately

Use the browser approval flow to obtain your key. Choose a client that supports remote Streamable HTTP and private request headers. Configure the MCP URL for your network with an Authorization bearer header. The shape below uses a placeholder; insert the real value through your client’s private secret settings, never a chat prompt or committed file.

Start with edel_connect to inspect the supplied key and edel_status to check account readiness. Hosted edel_connect does not issue a key or approve its own access. When a key expires, obtain fresh browser approval. On revocation, stop and obtain owner direction. See client connection details.

Remote MCP configuration — use your client’s secret store
{
  "mcpServers": {
    "edel": {
      "url": "https://mcp-testnet.edel-api.xyz/mcp",
      "headers": {
        "Authorization": "Bearer <client-held-api-key>"
      }
    }
  }
}

Ask useful questions before trading

Try these prompts after connecting:

“List the available markets and show BTC-USDCX-PERP’s current book, maker fee and taker fee. Do not place orders.”

“Show my open orders, positions and available margin. Flag anything that needs my attention.”

“List ready-to-run agent strategies and explain their rules. Keep estimates separate from promises.”

Tool call after your MCP client has initialized
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "edel_price",
    "arguments": { "marketId": "BTC-USDCX-PERP", "depth": 5 }
  }
}
ToolsWhat you can inspect
edel_connect / edel_statusCurrent-key metadata and account readiness.
edel_markets / edel_priceMarket catalogue, fees, price statistics and a book snapshot.
edel_account / edel_orders / edel_positionsYour approved account’s balance, working orders and positions.
edel_preview_orderAn order estimate without submission or reserved funds.
edel_agent_strategies / edel_agentsStrategy catalogue and your deployments; private agent reads require agents scope.
edel_agent_actions / edel_agent_feesDecision activity and model fees for your agent, with agents scope.

Inspect an agent strategy catalogue

The same connection can use agent tools. Request agents scope in the browser before reading or controlling your own deployments. A key stays bound to its approved account.

Try: “Show my agents and their latest activity. Ask me before pausing or stopping anything.” Lifecycle tools include edel_agent_command for pause, resume, stop and delete, subject to the same availability and guards as the app. Funding an agent needs the opt-in funding scope and the owner's passkey signature in the browser; a tool never signs. See trading agents.

Read the strategy catalogue through MCP
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "edel_agent_strategies",
    "arguments": {}
  }
}

Authorize a trading task explicitly

trade scope enables edel_place_order, edel_cancel_order, supported batch commands and edel_close_position. A close submits a reduce-only market order; it is not an instant position deletion. Define the markets, maximum size and price constraints before authorizing an action. A preview is an estimate, not permission to trade.

Try: “Preview a post-only buy within the market’s minimum size. Show the price, margin and fees, and wait for my approval before submitting.”

Every trading command needs its idempotency identity. Keep the original identity and body when retrying a lost response, and confirm effects through account state. Batch commands can partially succeed. The public tool reference lists each tool’s REST mapping; your client’s tools/list response provides its current input schema.

Use WebSockets for ongoing updates

MCP tools return request-time snapshots. For a continuous trading loop, use WebSockets, recover with one fresh snapshot after reconnect, then follow the stream. Do not repeatedly call market or account tools as a substitute for streaming.

If the hosted connection returns 401 unauthorized, check the private bearer header and key expiry. If a tool is refused, preserve its code and follow its recovery instructions instead of repeating the same call blindly. Passkey signatures and owner approval stay in your browser; a tool cannot sign on your behalf.