Claude Grain connectorWhat Claude can do in your Grain account.
The Claude Grain connector exposes 21 tools. 15 read your meetings, contacts, coaching and deals, 0 write anything, and 6 have no official description. Below: what Claude can pull up, what Grain keeps for its higher tiers, and where the sources disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What Grain changes for Claude
Grain keeps your meetings, their AI notes and their transcripts. The connector gives Claude access to that memory: transcripts, AI notes, attendees, companies and even the HubSpot deals linked to them. Ask which objections kept coming up in this week's customer calls, and Claude digs through them and answers with the relevant passages.
Find what was said, not just when. search_meetings runs a meaning-based search across every transcript, then fetch_meeting_transcript brings back the full text of one specific call.
Prep an account meeting in two minutes. search_companies finds the customer, list_meetings filters the calls you had with them, and fetch_meeting_notes returns the summarized notes, far shorter than a transcript.
Keep an eye on pipeline. On Grain's higher tiers, list_open_deals and fetch_deal read HubSpot deals, and list_coaching_feedback surfaces the sales coaching Grain generates.
What Claude does not do here: no documented tool writes to Grain. By default, the sheet only exposes reading, which is an observed floor rather than a promise. Six tools on the sheet are described nowhere, so this page says nothing about what they do. Claude also cannot see private meetings you were not invited to. And nothing fires after a call ends. That kind of hands-off chain needs an automation tool, a different trade; the Integrations hub covers that side. For a marketing CRM connector, see the Claude activecampaign connector.
Terms worth knowing
Five words and the rest of the page reads straight through.
- Connector
- The link you set up once between Claude and your Grain workspace, so Claude can draw on it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude picks which ones to call itself, and the directory sheet lists each one by name.
- Authorization
- Grain's own sign-in screen, where you hand Claude the access it will use afterwards. Granted once per person and revoked the same way.
- Approval
- The confirmation Claude waits for before it goes through with something that would change your account, shown in the chat right then.
- MCP
- The shared standard connectors are built on, which is what lets an assistant like Claude talk to an outside service such as Grain.
Connect Grain to Claude
- 01
Find Grain in your settings
In Claude's settings, open Customize, then Connectors, and search for Grain. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization first, then each member connects with their own account.
- 02
Sign in to your Grain account
Click Connect on the Grain row and sign in through the window Grain opens itself. Use the account that holds your work calls, since Claude will inherit its permissions.
- 03
Approve the authorization screen
Read Grain's authorization screen before you accept: it decides what the access covers, not Claude. If something breaks, use Disconnect and connect again; you can also revoke access from your Grain account.
The 21 tools of the Claude Grain connector
Grain gives Claude 21 tools: 15 that read your account, 0 that change something in it, and 6 no official source describes.
Fifteen lookup tools Grain describes, six names no source explains. Names stay exactly as Claude shows them.
- 15 read
- 6 not documented
What Claude reads (15)
15 toolsFifteen tools that look at meetings, people, coaching and deals without touching them.
myself
Returns the details of your own Grain account. Claude uses it to know whose access it is working with.
list_meetings
Returns a filtered list of the meetings your account can access. Claude narrows the list down before it opens any single call.
list_attended_meetings
Grain documents it on the same line as list_meetings, with the same description and filters: a filtered list of accessible meetings. The docs do not spell out what separates the two.
fetch_meeting
Brings back the full record of one meeting by its ID. It is the step after a list or a search, once Claude has singled out the right call.
fetch_meeting_notes
Retrieves the AI-generated notes Grain wrote for a meeting, much more compact than a transcript. Claude gets the gist without loading the whole text.
fetch_meeting_transcript
Loads the complete transcript of one meeting, not a summary of it. Claude can then quote a line exactly instead of paraphrasing it.
search_persons
Looks up the people who took part in your meetings, so that Claude can then filter the meeting list on one of them.
search_companies
Finds the companies that took part in your meetings. Claude then uses the result to filter the meeting list on one account.
search_meetings
Runs a meaning-based search across all your meeting transcripts at once, rather than one call at a time. Claude gets the passages that match an idea even when the exact words differ.
list_workspace_users
Lists every user in your Grain workspace. Claude can then tell colleagues apart from outside contacts.
list_coaching_feedback
Surfaces the sales coaching insights Grain's AI generates, across your meetings rather than for a single call.
fetch_meeting_coaching_feedback
Opens the detailed coaching scorecard for one specific meeting. It goes deeper than the overview and suits a debrief on a single call.
list_all_deals
Gives access to the HubSpot deal intelligence Grain holds, as long as the HubSpot integration is in place. Grain lists it next to list_open_deals without explaining the difference.
list_open_deals
Grain groups it with list_all_deals under a single description: access to HubSpot deal intelligence. The docs do not say how the two lists differ.
fetch_deal
Shows one HubSpot deal in detail from its ID, as Grain sees it. Claude can then cross it with the meetings held with that company.
Undocumented (6)
6 toolsThe directory publishes these six names and nothing else. No official source says what they do, and a name is not a description.
search
This name sits in the directory list, but no official source describes it: Grain's developer documentation details fifteen other tools and never mentions this one.
fetch
No page from Grain or Anthropic documents this tool. The directory publishes its name and stops there, and this page will not fill the gap with a guess.
search_recording_segments
Nothing in the documentation we read describes this name from the sheet. Neither Grain nor Claude's help center mentions it, so there is no telling whether it only reads or changes anything.
citation_search
A tool the directory lists without a single line of official description. Grain's developer docs skip it entirely, and no Anthropic text fills that silence on its side either.
suggest_calendar_event
The sheet lists it, yet no source describes this tool, and a name is not documentation. Whether it just reads or acts on your account is unknown.
suggest_email_draft
Same situation: the sheet names it, and no official text says what it does. Grain's tool reference skips it, and this page does not read meaning into the name.
What Claude checks with you first
By default, Claude stops and asks before any action it takes on an account on your behalf. Grain's fifteen documented tools only read.
On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked again. They can also cap what a connector does for the whole organization, and nobody overrides that from their own account. Grain, for its part, states that Claude requires explicit approval before any Grain tool, with a choice between once and the whole session: that is the publisher speaking, and Anthropic does not confirm it for this connector. Claude also works with your Grain permissions and nothing more.
Which Claude plans include Grain
None of the 819 directory sheets shows plan availability. Connector by connector, that information is not published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members connect. Grain's FAQ says something different, which the limits section sets side by side. For the up-to-date status on your account, check the connector's sheet in the official directory.
Where the Grain connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when a meeting wraps up.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's developer docs have a page on it, and the limits below come from Grain's developer documentation. The tool list is an observed floor, since an admin can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic notes on every sheet that it does not pick a publisher's tools or vouch for how they behave. The official description also mentions uses, like clipping highlights or building a customer project, that no documented tool covers.
Which Claude plans can use the Grain connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner enables each one first.
- Grain developer FAQ ↗undatedThe publisher states its server only works on paid Claude plans, Pro, Team and Enterprise, and not on a Free account.
What this page followsAnthropic's rule applies to every remote connector; Grain's undated FAQ says the opposite for its own server. Neither settles it for your account: check the directory sheet on your account.
Need help connecting Grain to Claude?
A person reads every message.
