MCP Gateway · Claude
Connect Grain to Claude
Sales reps and managers can ask Claude about their calls instead of scrubbing through recordings. With Grain added as a custom connector through the Speakeasy MCP Gateway, Claude reads meeting notes, action items and coaching scorecards, and each person sees only the Grain servers and tools their role can reach.
- Category
- Productivity
- Tools
- 22
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Grain MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Grain call inspected and logged.
Set up
Add Grain to Claude in 4 steps
- 01
Add Grain from the catalog
An admin finds Grain in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Grain uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Grain
Give teams the
mcp:connectscope on the Grain server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Grain to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Grain from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Grain needs its own OAuth grant, so each person connects it once. Until they do, Grain calls fail while the rest of the gateway keeps working.
From then on, Grain's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Grain
Draft the follow-up email
Right after a customer call, ask Claude to read the meeting notes and action items and draft a follow-up that lists what each side agreed to do and by when.
Review your coaching scorecard
Ask Claude what Grain's AI coaching feedback said about your last discovery call, and get the two points to work on before the next one.
Prepare for a deal review
Claude pulls a HubSpot deal synced in Grain, with its activity history, and summarizes where it stands so you walk into the forecast call ready.
Tools
22 tools
Each Grain tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
myself
Get information about the logged-in Grain user.
list_meetings
Returns a filtered list of Grain meetings you have access to, ordered by most recent.
list_attended_meetings
Returns a filtered list of Grain meetings you have attended, ordered by most recent.
fetch_meeting
Fetches information about a single Grain meeting by ID. The response format is the same as is returned by list_meetings.
fetch_meeting_notes
Fetches the AI notes payload from a single Grain meeting by ID. In some cases, older meetings may not have had notes generated for them. In these cases you can use fetch_meeting_transcript instead to determine the content of the meeting.
fetch_meeting_action_items
Fetches the action items extracted from a single Grain meeting by ID. Action items include the task description, timestamp, status (pending or completed), due date, and the person assigned to the action item (if any).
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Grain call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Grain tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Grain can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Do Claude users need a client ID to connect Grain?
Can Grain prompts in Claude be blocked?
How do Claude users get Grain?
Are Grain calls from Claude logged?
Connect more