# LeanTools documentation LeanTools documentation LeanTools hosts native tools and connectors for AI agents: LeanConnect (web search, email and connectors to third-party services), LeanBrowser, LeanModel (text, image, speech, music, video, avatar and realtime audio models), LeanMachine sandboxes, LeanVision camera analysis (beta), LeanMemory (warehouse, vectors, events and storage) and LeanData datasets. Your agent reaches all of them on one host with one API key: web search, email, data and connectors as MCP tools, and every service over a plain REST API. Every call is metered against prepaid credits. [Quickstart](https://leantools.ai/doc/quickstart) [MCP server](https://leantools.ai/doc/mcp) [REST reference](https://leantools.ai/doc/api) ## Pick your path [**Quickstart**Create a workspace, connect Claude, Codex or any MCP client, and make a first billed call in five minutes.](https://leantools.ai/doc/quickstart) [**MCP server**Streamable HTTP, JSON-RPC 2.0, bearer auth. The tool catalogue, call semantics, errors and limits.](https://leantools.ai/doc/mcp) [**Tools API and native tools**The same catalogue over plain HTTP, plus the native web_search.search and email.send tools.](https://leantools.ai/doc/tools) [**Connectors and approvals**Act inside third-party services with stored credentials, hold writes for a human, poll the decision.](https://leantools.ai/doc/connectors) [**Credits and billing**How prepaid credits, meters, caps, budgets and auto-reload work, and what each error code means.](https://leantools.ai/doc/credits) [**Workspace console**Keys, members and roles, tool and connector settings, billing, activity and the approval queue.](https://leantools.ai/doc/console) ## How it fits together A **workspace** is the unit of billing and access. It has members with roles, API keys, a prepaid credit balance and a set of enabled tools, connectors and datasets. Every request an agent makes carries an API key; LeanTools resolves the workspace, checks that the key may reach the tool, that the tool is switched on, that no cap or budget is exhausted and that credits remain, then runs the call and records one metering row. 1. **Connect once**Add the MCP endpoint `/mcp` and a key to your harness. Web search, email, datasets and connector actions you enable later are discovered automatically through `tools/list`; the other services take the same key over REST. 2. **Switch capabilities on**In the console, enable tools, link connector credentials, subscribe to datasets, and decide per function what agents may call, what needs approval and what stays off. 3. **Pay per call**Each call draws down credits at a published unit price. Keys can carry spend caps, tools monthly budgets, connectors rate limits and daily caps. Auto-reload keeps agents running. ## Two ways in | Surface | Best for | Where | | --- | --- | --- | | MCP server | Claude, Codex, Cursor and any MCP-capable agent framework. Tools are discovered, described and called over one endpoint. | [MCP server](https://leantools.ai/doc/mcp) | | Tools API | Agents and scripts that do not speak MCP but want the same catalogue with real HTTP status codes. | [Tools API](https://leantools.ai/doc/tools) | | REST API | Direct, typed access to each service: web search, LeanBrowser (HTTP and WebSocket), LeanModel (OpenAI-compatible, plus avatar streams over WebRTC and realtime audio over WebSocket), email, LeanMachine, LeanVision, LeanMemory (data stores and storage). | [Reference](https://leantools.ai/doc/api) | > The interactive OpenAPI description of every REST route, with schemas and a try-it panel, lives at [/swagger](https://leantools.ai/swagger) on this host.