product-management: add Grain to ~~meeting transcription Included servers alongside Fireflies#259
Open
adams wants to merge 1 commit into
Open
product-management: add Grain to ~~meeting transcription Included servers alongside Fireflies#259adams wants to merge 1 commit into
adams wants to merge 1 commit into
Conversation
…vers Add `grain` server block to `product-management/.mcp.json` and `Grain` to the "Included servers" column in `product-management/CONNECTORS.md` alongside Fireflies. Matches the existing multi-included-server pattern in this same file (e.g., `Linear, Asana, monday.com, ClickUp, Atlassian` in `~~project tracker`, `Amplitude, Pendo` in `~~product analytics`). The existing tool-agnostic `~~meeting transcription` placeholders already work as-is once Grain is wired — no skill, agent, or command changes required. Grain MCP: https://api.grain.com/_/mcp (launched June 2025). Refs anthropics#257 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
The
product-management/CONNECTORS.mdtable currently listsFireflies(Included) andGong, Dovetail, Otter.ai(Other options) for the~~meeting transcriptioncategory. Grain (grain.com) is a sibling option in the same category and slots in cleanly via the existing tool-agnostic placeholder pattern.Changes
grainserver block toproduct-management/.mcp.jsonpointing tohttps://api.grain.com/_/mcpGrainto the "Included servers" column inproduct-management/CONNECTORS.mdalongside Fireflies. This matches the existing multi-included-server pattern in other categories in the same file — e.g.,Linear, Asana, monday.com, ClickUp, Atlassian (Jira/Confluence)in~~project tracker,Amplitude, Pendoin~~product analytics.What stays the same
No changes to any skill, agent, or command. The
~~meeting transcriptionplaceholders insynthesize-research/SKILL.md,stakeholder-update/SKILL.md,write-spec/SKILL.md, andcompetitive-brief/SKILL.mdall work as-is once Grain is wired.Why this fits the plugin's coverage
Customer-research interviews and design-partner conversations frequently live in Grain rather than Gong — Grain has strong adoption in product teams running continuous discovery. Today, PM-plugin users with Grain have to paste transcripts into
synthesize-researchmanually, or wire a non-listed MCP themselves. The PR removes that friction.MCP details
Grain's MCP is publicly available at
https://api.grain.com/_/mcp. Auth is OAuth via Grain account. Reference: https://grain.com/release-note/06-18-2025 and https://developers.grain.com.Anticipated reviewer questions
.mcp.jsonalready ships both Fireflies and Grain after the patch — listing both in "Included servers" reflects what's actually bundled. Pattern is well-established elsewhere in this same file (Linear, Asana, monday.com, ClickUp, Atlassianin~~project tracker;Amplitude, Pendoin~~product analytics). Happy to swap to "Other options" if you'd prefer the more conservative placement.Linked to the coordinating issue covering this PR and the parallel
salesPR.Refs #257