MCP tools
Bring Edel Markets tools into a compatible assistant with account-scoped access.
Use market and account tools from an assistant
From an assistant to product tools
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
Model Context Protocol (MCP) gives compatible assistants a structured way to call Edel Markets tools. Our hosted service maps those tools to the public API: inspect markets and account snapshots, preview an order, or submit an authorized trading action with the required scope.
MCP is an optional way to use the same product capabilities. Account permissions, trading risk checks and owner-controlled funding remain in place. Edel Markets is on Devnet, with Testnet and Mainnet coming soon; use the MCP endpoint supplied for your approved environment.
Connect with a privately stored key
- 01Complete the owner-approved agent connection and receive a scoped key for the intended account.
- 02Choose a client that supports remote Streamable HTTP, private request headers and tool-approval controls. Check those capabilities in the client you intend to use.
- 03Configure the supplied MCP endpoint and send the API key as an Authorization bearer on every request, using the client's private secret storage.
- 04Start with read-only tools to confirm the credential and account readiness.
Every request is authorized by its bearer key, even when it includes an MCP session identifier. Store the key in the client’s private credential settings and never paste it into an assistant prompt. See MCP client configuration for the setup details.
Start with connection checks and snapshots
All hosted MCP calls require an approved read-capable key, including market snapshots. These tools help establish what the connected client can see before it takes a trading action.
| Tool | Purpose |
|---|---|
| edel_connect | Inspect the key already supplied by your client; it does not approve or start an agent grant. |
| edel_status | Check account and secure-setup readiness. |
| edel_markets / edel_price | Read the market catalogue, market statistics and book snapshots. |
| edel_account / edel_positions / edel_orders | Inspect snapshots of the approved account, current positions and open orders. |
| edel_preview_order | Estimate an order without submitting it or reserving funds. |
Trade within the approved task
With trade scope and your authorization for an action or defined strategy, tools can place or cancel orders, submit supported batches, and close a position through a reduce-only market order. Keep each order within the approved markets, sizes and constraints. Read and preview results do not authorize a trade.
Read the result as rejected, accepted, partially filled, filled, cancelled or unknown, and follow account updates to confirm the effect. Batch results are independent and can partially succeed. If a response is lost, keep the original order identity while reconciling the outcome. The MCP tool reference contains the supported operations and exact semantics.
Live updates and owner controls
MCP tools return request-time snapshots. Ongoing market and account updates use WebSockets through a direct client; MCP does not replace that live connection or manage its socket tickets. This distinction matters for a continuously running strategy that must respond to fills, changing exposure or stale data.
Deposits, withdrawals, passkey actions, agent approval and key management stay with the owner in the browser. When a key expires, approve a fresh grant and update the client's private credential. After revocation, stop and obtain owner direction before reconnecting. Continue with the full MCP reference, agent permissions or market-making workflows.