Skip to main content
Back to the Grain MCP server

MCP Gateway · Claude Cowork

Grain icon

Connect Grain to Claude Cowork

Weekly pipeline and enablement work spans dozens of recordings, which suits Cowork's longer tasks. With Grain delivered through a plugin from Speakeasy's synced marketplace, a Cowork session can read many calls in one run, and agent hooks send each prompt to Speakeasy to allow or deny before a step runs.

Category
Productivity
Tools
22
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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.

Deploy on MCP Gateway

Set up

Add Grain to Claude Cowork in 4 steps

  1. 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.

  2. 02

    Choose who can use Grain

    Give teams the mcp:connect scope on the Grain server through team access or a role. Claude Cowork connects to the Grain server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Grain from Claude Cowork

    The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Grain

Run the weekly pipeline review

Cowork lists every open HubSpot-linked deal synced in Grain, fetches each one's activity, and writes a review that flags deals with no recent calls.

list_open_dealsfetch_deal

Assemble a voice-of-customer reel

Give Cowork a theme like pricing objections. It searches transcripts, creates a clip at each relevant moment, and gathers them in a new collection for the product team.

search_meetings_v2create_clipadd_recordings_to_collection

Audit open action items

Cowork goes through a week of meetings, pulls every action item still pending, and groups them by assignee and due date for Monday's stand-up.

list_meetingsfetch_meeting_action_items

Tools

22 tools

Each Grain tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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).

See all 22 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can Cowork use Grain from a personal Claude account?
Personal Claude accounts can't be governed in Cowork. Grain reaches Cowork through the organization's plugin marketplace synced into Claude.
When does Cowork pick up a change to the Grain plugin?
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
How do Claude Cowork users get Grain?
An admin adds Grain from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Grain tools their access allows.
Are Grain calls from Claude Cowork logged?
Yes. Grain calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Grain in other clients

AI everywhere.

Control here.