SDKs
Four client SDKs cover the Mangrove ecosystem. A turnkey agent template (mangrove-agent) ties them together — it has its own tab.
| SDK | Language | Distribution | Best for |
|---|---|---|---|
mangroveai | Python ≥3.10 | pip install mangroveai | The MangroveAI platform — strategies, backtesting, AI copilot, on-chain, DeFi, social |
mangrove-kb | Python ≥3.10 | pip install mangrove-kb | Local signal evaluation and indicator computation, no API call |
mangrovemarkets | Python ≥3.10 | pip install mangrovemarkets | DEX aggregation, marketplace, wallet, portfolio analytics — client-side signing |
@mangrove-ai/sdk | TypeScript / Node | npm install @mangrove-ai/sdk | Same surface as mangrovemarkets, in TypeScript |
Choosing between mangroveai and mangrove-kb
- Use
mangroveaiif you want managed strategies, backtests, the AI copilot, or any feature of the hosted platform. Requires an account and API key. - Use
mangrove-kbif you want to compute indicators or evaluate signals on your own data, locally, with no network round-trip. Pure compute, MIT-licensed. - Use both if you want platform features for orchestration but local compute for hot loops.
Choosing between SDK and direct MCP
- Use an SDK for backend code, notebooks, scripts.
- Use the MCP server when an LLM agent or MCP-capable client is in the loop. The MCP servers expose the same capabilities (where they overlap) as tool calls.
Turnkey: just run the agent
If you don’t want to assemble the SDKs yourself,mangrove-agent is a FastAPI + MCP template that wires the platform together. Clone, set your API key, and you have a working trading bot in 60 seconds.