Add Granola MCP server docs page#425
Closed
socialyadept wants to merge 1 commit into
Closed
Conversation
Adds a new two-tab MCP server guide for Granola (native hosted MCP server vs. C1's REST API translation), following the existing Notion guide's structure, and adds it to site navigation. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
![C1 Squire [DEV]](https://avatars.githubusercontent.com/in/2846581?s=40&u=9dfdc6298bb22a241aaf41a6558bc1563c5c6466&v=4){kind=avatar}
Contributor
Author
|
Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Granola (an AI meeting-notes app) has no existing setup page in these docs. This adds a new two-tab page, following the pattern established for Notion, so admins can tell apart and set up either way C1 can govern Granola access:
mcp.granola.ai). Authentication is per-user OAuth with dynamic client registration (DCR) only — Granola's hosted server doesn't offer a bearer token or API key mode, so there's nothing to create in Granola first. Listed as plain Granola in the MCP server catalog.A comparison table above the tabs explains the difference up front (who hosts the server, authentication, access scoping, tool surface, setup effort), and the intro prose is explicit that plain "Granola" in the catalog refers to the native MCP option, distinct from "Granola API."
Also adds the new page to site navigation, inserted alphabetically in the MCP server guide list.
Reviewer note: unlike other vendors in this docs batch, there was no pre-existing internal research for Granola's MCP setup — this page is based on best-effort research against Granola's own public help-center and blog documentation (no vendor confirmation). The DCR-only authentication method and tool list are well-documented by Granola, but Granola's docs don't describe a centralized, self-service way to revoke an individual MCP connection from Granola's own settings (only reconnecting/disconnecting from the AI client side is documented), so that section is intentionally conservative. Please give the Granola MCP tab extra scrutiny before merging.
Test plan
docs.granola.ai,www.granola.ai) resolve live/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#..., etc.) exist onmainTabs/Tab/Steps/Step/Note) are balanceddocs.jsonis valid JSON and the new nav entry is inserted alphabetically without reformatting surrounding lines🤖 Generated with Claude Code