Skip to main content

Notion

Connect Grain's MCP server to a Notion Custom Agent so it can pull meeting context into its workflows.

You can connect Grain to a Notion Custom Agent so it can pull meeting transcripts, notes, and action items into whatever workflow that agent runs.


Before you start

Each Custom Agent needs its own connection to Grain, this is not a workspace-wide integration. The connection runs on the credentials of whoever set it up.

MCP connections for Custom Agents are available on Notion Business and Enterprise plans only. Grain isn't in Notion's list of pre-configured connections, so you'll connect it as a custom MCP server.


Turn on custom MCP servers for your workspace

A workspace admin has to enable custom MCP servers before anyone can connect Grain to an agent.

  1. As a workspace admin, go to 'Settings', then 'Connections'.

  2. In the 'Manage' tab, toggle on 'Enable custom MCP servers'.

  3. Optionally, add Grain's MCP server URL to your workspace's approved connections list so members don't need individual admin approval to add it.

Note: If your workspace limits members to admin-approved connections only, add Grain's server URL under 'Approved connections' before anyone tries to connect it to an agent.


Connect Grain to a Custom Agent

Do this for each Custom Agent that needs Grain data.

  1. Open the Custom Agent's 'Settings'.

  2. Go to 'Tools & Access'.

  3. Select 'Add connection', then 'Custom MCP server'.

  4. Enter Grain's MCP server URL (https://api.grain.com/_/mcp) and, optionally, a display name.

  5. Complete authentication with your Grain account.

  6. Select 'Connect'.

Once connected, review the list of tools Grain exposes and turn on the ones this agent needs. Read tools, like searching meetings or fetching a transcript, can safely run automatically. Write tools default to requiring your approval before they run.

Note: Only the person who authenticated the connection can change its tool settings, even if other people have Full Access to the agent.


Test the connection

Once Grain is added to an agent, confirm it's working before relying on it.

  1. Open a chat with the Custom Agent, or trigger it manually.

  2. Ask a simple test prompt, for example, "What was my most recent Grain meeting?"

  3. Check that the agent's response includes specific meeting details rather than a generic answer, which confirms it actually called Grain rather than answering from general knowledge.

  4. Open the agent's 'Activity' tab and confirm you see the Grain tool call logged there.

Note: If the agent doesn't call Grain, confirm the connection shows a "Connected" status in 'Tools & Access,' and that the relevant Grain tools are toggled on. If it's still not working, try disconnecting and reconnecting Grain.


How results are surfaced

Grain's read tools, like searching meetings or fetching a transcript, run automatically by default and their results come back directly in the agent's chat response. You won't see a separate approval prompt for these unless you've changed that tool's setting to 'Always ask.'


FAQ

Do I need to connect Grain separately for every agent? Yes. MCP connections in Notion are unique to each Custom Agent and use the credentials of whoever authenticated them. There's no workspace-wide Grain connection the way there is with other integrations.

Can I use Grain with a Custom Agent on any Notion plan? No. MCP connections for Custom Agents require a Business or Enterprise plan.

What happens if I disconnect Grain from one agent? Only that agent loses access. Other agents with their own Grain connections are unaffected.


Next up: Perplexity

Did this answer your question?