--- title: "MCP server docs: eight tools, one endpoint - actionlake" description: "Docs for the actionlake MCP server: eight tools, a four-step quickstart, the REST API and OpenAPI spec. Connect Claude or another MCP client in one line." canonical: https://actionlake.com/docs updated: 2026-10-23 --- MCP server documentation /docs # Short on purpose. The actionlake MCP server lives at one URL and gives an agent eight tools: help, find_actions, get_action, do, ask, check, cost and account. Add it to Claude Code with one command, or to any MCP client that speaks Streamable HTTP, and sign in with OAuth 2.1 or a bearer key. Everything is also on REST. [Start free](https://actionlake.com/console?start=sandbox) [Read the quickstart](https://actionlake.com/docs/quickstart) Or connect from Claude Code; no key needed, the consent page creates a free account `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` what the agent sees on connect ``` help {} actionlake · 8 tools · 1,000+ connectors · 289,000+ actions billed: do, ask free: everything else, and every cached answer find_actions what can I do? get_action how exactly do I do it? do do it ask answer a question across systems check will this work? (free) cost what will it cost? account tenant · keys · connections · plans ``` Illustrative: the shape of the help reply, not a transcript. 1. [01 Quickstart Connect an agent, run a public action, connect a system, read the receipt. four steps](https://actionlake.com/docs/quickstart) 2. [02 Connect an agent Claude, ChatGPT, Copilot, Cursor, Gemini, Grok and more: the exact steps for each. every MCP client](https://actionlake.com/docs/connect) 3. [03 API reference The REST twin: same names, same receipts, same price book. REST · openapi.json](https://actionlake.com/docs/api) 4. [04 Connectors What agents can reach, and how a new system joins. 1,000+ connectors](https://actionlake.com/connectors) The surface ## Eight tools. Named for what an agent wants. Only two spend money, and they cannot be confused: `do` is a verb, `ask` is a question. The other six are free, always, including the dry run. 01 `help` orientation, a topic, or "why did that fail?" free 02 `find_actions` plain-language search over 289,000+ actions free 03 `get_action` the schema, output shape, cost and an example free 04 `do` one action, or several in order per upstream call 05 `ask` fetch from several systems and join them; the answer, not the rows per upstream call 06 `check` dry run: inputs, permissions, connections, cost, what needs a confirmation free 07 `cost` spend, forecast, cap headroom, the price book free 08 `account` tenant, keys, connections, plans, schedules, approvals, billing free The agent is the planner. `ask` takes structured steps and a join, not a sentence; `find_actions`, `get_action` and `check` exist to make writing that plan cheap. REST and MCP are one implementation; a test holds them to it. Connect ## If your agent speaks MCP, you are already integrated. Claude, ChatGPT, Copilot, Cursor, Gemini, Grok, Codex and any other MCP client take the same URL. Send a key, or sign in on the consent page, which creates a free account on the spot. - **OAuth 2.1** sign-in, or a key in `Authorization` or `X-API-Key` - **26** ways in, step by step, on [Connect an agent](https://actionlake.com/docs/connect) - **8** tools, however many systems you connect - **100,000** free calls on the sandbox, no card terminal ``` claude mcp add --transport http actionlake https://connect.actionlake.com/mcp ``` 1. 1 Run the command once. Add `--scope user` before the name to use ActionLake in every project. 2. 2 Signing in instead of using a key? Leave the header off, start `claude` and run `/mcp`; the ActionLake consent page opens, and it can create a free account there. 3. 3 Ask your agent to call `help`. The eight tools are listed under `actionlake`. Verified in ActionLake's code · [every platform, step by step](https://actionlake.com/docs/connect#claude-code) For software ## Machine-readable, on principle. We sell infrastructure for software, so the documents that matter are fetchable by software, before you sign anything and without a key. - [api.actionlake.com `/v1/price-book` every commercial number, as JSON, no key](https://api.actionlake.com/v1/price-book) - [api.actionlake.com `/openapi.json` the REST surface, generated from the same code the tools call](https://api.actionlake.com/openapi.json) - [api.actionlake.com `/v1/llms.txt` what an agent reads on connect: the tools, the pricing, how to start](https://api.actionlake.com/v1/llms.txt) - [actionlake.com `/llms.txt` this site, indexed for agents](https://actionlake.com/llms.txt) - [actionlake.com `/.well-known/actionlake-trust.json` the mechanisms, and the absences, machine-readable](https://actionlake.com/.well-known/actionlake-trust.json) - [actionlake.com `/.well-known/security.txt` disclosure scope and safe harbour](https://actionlake.com/.well-known/security.txt) For AI agents ## An agent can set itself up. If you are an agent reading this: you do not need a person or a key to start. 1. Connect to `https://connect.actionlake.com/mcp` with no credentials. `help`, `find_actions` and `tenant.create` need none. 2. Call `account {"op": "tenant.create", "name": "…"}`. It returns a tenant and its key, shown once. Over REST it is `POST https://api.actionlake.com/v1/account/tenant.create`. 3. Write the key into your own MCP config as `Authorization: Bearer al_…` (or `X-API-Key`) and reconnect. [Connect an agent](https://actionlake.com/docs/connect) has the exact file for your client. 4. Or ask your user to sign in: connect without a header, and the client opens the actionlake consent page, which signs them in or creates a free account in one click. Connecting a vendor that uses OAuth, such as Xero, still needs a person once: register your own app with the vendor, sign in as an admin, and the tokens are stored as a connection. API-key vendors the agent connects itself with `connections.create`. what the agent does ``` # 1 connect with no key: help, find_actions and tenant.create need none mcp https://connect.actionlake.com/mcp # 2 give yourself a tenant account {"op": "tenant.create", "name": "my-agent"} ✓ key: al_… shown once - keep it # 3 put the key in your own MCP config, then reconnect headers {"Authorization": "Bearer al_…"} # or 3 have your user sign in instead: no header, # the consent page signs them in or creates a free account ``` 07Questions ## Before the first call. The questions people ask while they connect, with the answer an agent would give. **How do I add actionlake to Claude Code?** Run claude mcp add --transport http actionlake https://connect.actionlake.com/mcp, start Claude, and approve the consent screen. No key yet? The consent screen creates a sandbox with 100,000 free calls a month. Then say help {} to see the eight tools. **Does actionlake work with MCP clients other than Claude Code?** Any MCP client that supports remote servers over Streamable HTTP can add https://connect.actionlake.com/mcp and sign in with OAuth 2.1 (with dynamic client registration) or a bearer key. The Connect an agent page has the steps for each client, and says which ones we have not yet tested. Anything that can make an HTTPS request can use the REST API. **Do I need an API key to start?** No. Over MCP, the consent screen creates a sandbox account. Over REST, one unauthenticated call to tenant.create returns an account and a key with 100,000 free calls a month. The key is shown once, so keep it. **How does my agent know what an action costs before running it?** get_action shows each action's cost, and check runs a dry run: it validates inputs, permissions and connections, estimates calls and cost, and says what needs a confirmation. Both are free and send nothing to the vendor. **How do I limit what an agent can do?** Mint a key for it with allowed_actions (one action, a whole connector, a verb, read-only, or everything), a cap in calls, and a confirm policy: agent, human_for_writes or human. Revoking a key also revokes every key it minted. **What happens when a vendor rate-limits or fails?** A vendor's 401, 403, 429, 5xx or a timeout is not billed. Reads are cached per action, so repeats do not touch the vendor. Writes are never cached and never retried. Every error says what to do next. **Is there an OpenAPI spec and an llms.txt?** Yes: an OpenAPI description of the REST API, an llms.txt for agents, a public JSON price book and a machine-readable trust document. Each is linked in the Machine-readable section of this page, and none needs a key. ## Ask one question across two systems. [Start free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls. No card. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/docs More: https://actionlake.com/llms.txt