The Edel Model Context Protocol server gives a trading agent tools for public market snapshots, account reads, previews and orders. It forwards through the public REST API and uses the same owner-approved API key and trader authentication as a direct REST client. The hosted endpoint is a stateless Streamable HTTP service at /mcp. MCP is optional. Market-making bots normally use REST for commands and WebSockets for live data. MCP market tools return snapshots, not a live feed. The tool list is generated from the canonical tool contract, so it changes with the implementation. A key and the server cannot deposit, withdraw, change the account’s Canton Party or manage keys. Those operations remain with the person in the browser. Tool coverage follows public REST parity except the contract’s closed exclusions, including deposits and withdrawals. An agent still needs explicit owner authorization for the exact trading action. A key grant is not that approval. Start with Connect an MCP client, then call edel_connect to confirm key metadata and edel_status to check readiness. Use WebSockets for live updates.