6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query meeting transcripts, AI notes, deals and coaching scorecards.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Grain MCP server connects meeting recordings, transcripts and revenue intelligence to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 21 tools covering meetings, notes, transcripts, people, companies, HubSpot deals and sales coaching scorecards. Sign-in is OAuth. The directory labels it read only; Grain's own release notes describe write actions.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
suggest_calendar_event and suggest_email_draft are undocumented by Grain and unreadable over the wire. We could not establish whether they write.scopes_supported is absent from both OAuth descriptors, and the underlying REST flow has no scope parameter. Authorisation is all-or-nothing at your own permission level.helpful_usage_information parameter 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-remote is deprecated by the vendor. Grain flags it as not officially supported and due to be replaced by native integrations.works_with covers Claude and the Claude API only, despite the directory publishing a claude mcp add string.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.
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.
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.
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.
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.
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.
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.
mcp-remote deprecation notice, the nine report prompts and every FAQ answer above (retrieved 2026-08-18) · retrieved 2026-08-18calendar_event include on a recording (retrieved 2026-08-18) · retrieved 2026-08-18-how-to-use-coaching slug 301-redirects here) · retrieved 2026-08-18https://api.grain.com/_/mcp — an anonymous initialize returned HTTP 401 with WWW-Authenticate: Bearer naming a resource metadata document. Both the root and path-insert forms of .well-known/oauth-protected-resource and .well-known/oauth-authorization-server returned HTTP 200 on api.grain.com and grain.com; the append form returned 404. Neither descriptor carries a scopes_supported key (2026-08-18) · retrieved 2026-08-18grain.com/robots.txt and support.grain.com/robots.txt both allow the paths used here and carryprompt_names array and the works_with list (snapshot 2026-08-16) · retrieved 2026-08-16Connect Grain once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.