Grain
by Grain
Query meeting transcripts, AI notes, deals and sales coaching scorecards from your AI assistant. 21 listed tools, OAuth sign-in, and a Read only label the vendor's own release notes contradict.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Grain via MCP
https://api.grain.com/_/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Grain Tools & Capabilities (21)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The "Read only" label is wrong, and we could not fully bound the write surface. Grain's release notes describe four MCP actions that change state, none of which appears in its tool documentation or in Anthropic's 21 names. Treat the write surface as at least four actions and possibly more.
- Two tools are unresolved.
suggest_calendar_eventandsuggest_email_draftare undocumented by Grain and unreadable over the wire. We could not establish whether they write. - Six of 21 listed tools are undocumented. Grain's guide covers 15. The remaining six have no published description, parameters or plan gate.
- No scopes at all.
scopes_supportedis absent from both OAuth descriptors, and the underlying REST flow has noscopeparameter. Authorisation is all-or-nothing at your own permission level. - You cannot exclude specific meetings. Grain states no per-meeting or per-company MCP exclusion exists. Tool toggles in the client are the only filter.
- Deals and coaching need Business or Enterprise, and deals also need HubSpot. Free and Starter accounts receive an error, not an empty result, so the failure looks like a bug.
- Telemetry is on with no opt-out. Grain returns a
helpful_usage_informationparameter in tool responses to study usage patterns. It states this is never used as AI training data and that an opt-out is planned, but none exists today. mcp-remoteis deprecated by the vendor. Grain flags it as not officially supported and due to be replaced by native integrations.- Not listed for Claude Code or Claude Desktop. Anthropic's
works_withcovers Claude and the Claude API only, despite the directory publishing aclaude mcp addstring. - ChatGPT team sharing does not work. Grain reports that a connector set up by an admin works only for that admin, and that the connection must be enabled before a conversation starts rather than mid-conversation. Grain attributes both to OpenAI and recommends Claude for MCP work.
- The prompt listing is empty in the directory. Anthropic's snapshot records zero prompts against Grain's nine documented reports.
- We could not read tool schemas or safety annotations. The endpoint is gated, so the tool count and names are the directory's and no tool on this page is annotated. What we verified live was the auth posture, both OAuth descriptors and all three well-known path forms.
- This page describes data access only. It is not legal advice on recording consent or on employment data.
Frequently asked questions
Is the Grain MCP connector really read only?
No, and Anthropic's directory label is wrong on this point. Grain's own release notes describe four MCP actions that change state: creating clips from a meeting, tagging meetings in bulk, inviting people to the workspace, and setting capture and sharing defaults for teams and users. Grain's quick start guide documents none of them.
What Claude plan do I need for the Grain integration?
A paid one. Grain states that MCP integrations are available only on Pro, Team and Enterprise Claude plans, and that free Claude accounts cannot connect external tools or data sources at all. Grain also recommends Claude over ChatGPT, describing Claude's MCP support as meaningfully more mature and robust at the time of writing.
Are all Grain MCP tools available on every Grain plan?
No. Grain states that meeting search, transcripts, notes and contact tools work on Free, Starter, Business and Enterprise. The five deal and coaching tools are restricted to Business and Enterprise. Grain says Free and Starter users receive an error rather than an empty result when they call a premium tool, so failures look like breakage.
What meeting data can the Grain MCP server see?
Everything you can already open in Grain, and nothing more. Grain states the server accesses only data you have permission to view in your workspace, has no access to private meetings you were not invited to, and reaches no other workspace. It inherits your existing account permissions rather than adding a separate access layer.
Can I stop the connector from reading specific meetings?
Not today. Grain states you cannot currently exclude specific meetings or companies from MCP access. The available controls are coarser: enable or disable individual tools in your client's integration settings, and adjust the underlying Grain workspace permissions. Grain advises reviewing those permissions before connecting and writing narrowly scoped prompts.
Does list_coaching_feedback expose scores about my colleagues?
It exposes whatever coaching data your Grain account can already open, which for a manager includes scorecards on named reps. Grain scores every external call from one to five across rapport, qualification, needs, value, objections and closing, and calculates talk time, filler words and monologue length per person. Nothing here is anonymised.
What is the helpful_usage_information parameter in Grain tool responses?
It is Grain telemetry about how its tools are being used, returned alongside tool results. Grain states the data is never used as AI training data, that no opt-out currently exists, and that one is planned. Grain's own advice to anyone uncomfortable with the collection is to wait until the opt-out ships before connecting.
Sources
- Grain MCP quick start guide, for the 15 documented tools and their parameters, the plan gates, the Claude and ChatGPT setup steps, the
mcp-remotedeprecation notice, the nine report prompts and every FAQ answer above (retrieved 2026-08-18) · retrieved 2026-08-18 - Grain public API reference, for the OAuth2 authorization-code flow with PKCE and its parameter list, the statement that tokens carry the same access as the authenticated user, the 23 REST endpoints, and the read-only
calendar_eventinclude on a recording (retrieved 2026-08-18) · retrieved 2026-08-18 - Grain release notes, for the four MCP write actions — clip creation and bulk tagging (2026-05-13), workspace management including invites and capture and sharing defaults (2026-07-15) — and for the statement that timestamps replaced citations in notes and action items (retrieved 2026-08-18) · retrieved 2026-05-13
- Grain Coaching help article, for the one-to-five scorecard sections, the coaching-opportunity flag threshold, the five per-person interaction metrics and the Business-plan gate (retrieved 2026-08-18; the
-how-to-use-coachingslug 301-redirects here) · retrieved 2026-08-18 - Grain consent and privacy page, for the participant-first access principle, the personalised recording disclaimer, the Zoom native consent reporting note and the no-sale statement (retrieved 2026-08-18) · retrieved 2026-08-18
- Live auth posture check against
https://api.grain.com/_/mcp— an anonymousinitializereturned HTTP 401 withWWW-Authenticate: Bearernaming a resource metadata document. Both the root and path-insert forms of.well-known/oauth-protected-resourceand.well-known/oauth-authorization-serverreturned HTTP 200 onapi.grain.comandgrain.com; the append form returned 404. Neither descriptor carries ascopes_supportedkey (2026-08-18) · retrieved 2026-08-18 grain.com/robots.txtandsupport.grain.com/robots.txtboth allow the paths used here and carry- Anthropic Connectors Directory entry, for the 21 tool names, the partner tier, the "Read only" permissions field, the empty
prompt_namesarray and theworks_withlist (snapshot 2026-08-16) · retrieved 2026-08-16 - Grain support — <mailto:help@grain.com> · Privacy policy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Grain
- Tools
- 21
- Domain
- api.grain.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.