Connectors · Marketing & media
Grain MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Grain and the rest of your systems. It gives your agent 22 Grain actions (10 reads, 8 writes and 4 that wait for a confirmation) and holds the Grain credential itself, so the agent never does. It paces Grain's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "grain.users.list", intent: "check which Grain account is connected"}# List users · read · 1 upstream call- 22actionsin one signed file
- 10readlook, never change
- 8writecreate and update
- 4wait for a yesdestructive, confirmed first
Set up
Connect Grain in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Grain.
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
access_tokenGrain access token
account { op: "connections.requirements", service: "grain" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "grain.users.list" }# list users · read · 1 upstream callcheck { action: "grain.hooks.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Grain at a glance
- Sign-in
- Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
- You provide
access_token- Limits we pace to
- 120 calls a minute, per connection
- API covered
- Grain Public API v2, Public-Api-Version 2026-10-01
api.grain.com - Built from
- Grain's documentation, read 23 October 2026developers.grain.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 7 of 10 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 4, so ask can line Grain up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Grain.
22 actions in 9 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 10readlook, never change
- 8writecreate and update
- 4destructivewait for a confirmation
Uploads
52 read · 3 write · 0 destructive
Create an upload · List uploads · Get an upload · Promote a staged upload
Recording shares
40 read · 2 write · 2 destructive
Share a recording with a team · Share a recording with a user · Unshare a recording from a team · Unshare a recording from a user
Recordings
43 read · 1 write · 0 destructive
List recordings · Get a recording · Rename a recording · Get a recording's transcript
Hooks
31 read · 1 write · 1 destructive
Create a hook · List hooks · Delete a hook
Recording tags
20 read · 1 write · 1 destructive
Add a tag to a recording · Remove a tag from a recording
Meeting types
11 read · 0 write · 0 destructive
List meeting types
Teams
11 read · 0 write · 0 destructive
List teams
Token
11 read · 0 write · 0 destructive
Get the token's identity
1 more area · 1 actions
- Users 1
Top actions
The Grain API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 6 of Grain's 6 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
grain.users.listList users | List users. | read | identity.user.list474 connectors |
grain.token.infoGet the token's identity | Get the token's identity. | read | identity.current_user.get307 connectors |
grain.recordings.listList recordings | List recordings. | read | comm.meeting_recording.list11 connectors |
grain.recordings.getGet a recording | Get a recording. | read | comm.meeting_recording.get10 connectors |
grain.recordings.get_transcriptGet a recording's transcript | Get a recording's transcript. | read | comm.meeting_transcript.get11 connectors |
grain.teams.listList teams | List teams. | read | this connector |
grain.hooks.listList hooks | List hooks. | read | this connector |
grain.hooks.createCreate a hook | Create a hook. | write | this connector |
grain.uploads.listList uploads | List uploads. | read | this connector |
grain.uploads.createCreate an upload | Create an upload. | write | this connector |
grain.recording_tags.addAdd a tag to a recording | Add a tag to a recording. | write | this connector |
grain.hooks.deleteDelete a hook | Delete a hook. | destructive | this connector |
Try it
Prompts to paste into Claude.
Each one names the Grain actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Who has access in Grain? List every user and their role.
calls
grain.users.list - Writewrite
Create a hook in Grain. Show me exactly what you will send before you save it.
calls
grain.hooks.create
Governance for Grain
Destructive actions wait for a yes.
4 Grain actions are destructive. These are all of them:
- Delete a hook
grain.hooks.delete - Remove a tag from a recording
grain.recording_tags.remove - Unshare a recording from a team
grain.recording_shares.unshare_with_team - Unshare a recording from a user
grain.recording_shares.unshare_with_user
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Delete a hook?
intent: the user asked me to delete a hook
account { op: "keys.create", name: "grain-agent", allowed_actions: ["grain.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "grain.hooks.delete", approver: "[email protected]" }, { match: "grain.recording_tags.remove", approver: "[email protected]" }, { match: "grain.recording_shares.unshare_with_team", approver: "[email protected]" } ]}Cost
What Grain costs on actionlake.
Every Grain action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Grain refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 22 Grain actions
- 22actions pageeach page of a long list is one call
- 7reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Grain action.
22 actions by area: the id your agent calls, what it does, and its effect.
Uploads5
grain.uploads.createCreate an uploadwritegrain.uploads.getGet an uploadreadgrain.uploads.listList uploadsreadgrain.uploads.promotePromote a staged uploadwritegrain.uploads.updateUpdate an uploadwrite
Recording shares4
grain.recording_shares.share_with_teamShare a recording with a teamwritegrain.recording_shares.share_with_userShare a recording with a userwritegrain.recording_shares.unshare_with_teamUnshare a recording from a teamdestructivegrain.recording_shares.unshare_with_userUnshare a recording from a userdestructive
Recordings4
grain.recordings.getGet a recordingreadgrain.recordings.get_transcriptGet a recording's transcriptreadgrain.recordings.listList recordingsreadgrain.recordings.updateRename a recordingwrite
Hooks3
grain.hooks.createCreate a hookwritegrain.hooks.deleteDelete a hookdestructivegrain.hooks.listList hooksread
Recording tags2
grain.recording_tags.addAdd a tag to a recordingwritegrain.recording_tags.removeRemove a tag from a recordingdestructive
Meeting types1
grain.meeting_types.listList meeting typesread
Teams1
grain.teams.listList teamsread
Token1
grain.token.infoGet the token's identityread
Users1
grain.users.listList usersread
Questions
The Grain MCP server, answered.
Is there a Grain MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 22 Grain actions across uploads, recording shares, recordings and hooks, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Grain.
What do I need to connect Grain?
Grain access token. The free call account { op: "connections.requirements", service: "grain" } lists exactly what to paste.
Can an AI agent delete or change things in Grain?
Only if its key allows it, and only with an explicit confirmation. 4 Grain actions are destructive, including delete a hook, remove a tag from a recording and unshare a recording from a team. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Grain API limit?
actionlake paces every call to the limits in the Grain service file: 120 calls a minute per connection. Repeated reads are answered from cache (7 Grain actions can be), which never reaches Grain.
What does a Grain action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (22 Grain actions page). Cache hits, searches, dry runs and calls Grain refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Grain API does it cover?
The Grain Public API v2, Public-Api-Version 2026-10-01 at api.grain.com. It is built from Grain's documentation as read on 23 October 2026. 22 actions in 9 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Grain data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Grain credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Grain today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.