Rename "Programmatic GTM" to "MCP & Plugins"#717
Conversation
Rename the Programmatic GTM concept to MCP & Plugins and remove GTM-specific framing so the copy applies to building any agents, not just GTM. - Rename get-started/core-concepts/programmatic-gtm.mdx -> mcp-plugins.mdx - Flatten integrations/mcp/programmatic-gtm/* -> integrations/mcp/* - Rewrite copy to drop GTM branding (titles, descriptions, examples, FAQs) - Update all internal links across guides, changelog, invent, mcp-client - Rename nav group Programmatic GTM -> MCP & Plugins - Add redirects from all old routes to the new paths Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVsFqM7fyBzhVdaQ5GWBMx
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
The Documentation Lint check runs on changed files. Renaming pages pulled invent.mdx into the diff, surfacing a pre-existing non-standard embed wrapper. Normalize it to the standard snippet (paddingTop: '56.25%', single-quoted border and borderRadius) so the lint check passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVsFqM7fyBzhVdaQ5GWBMx
🎯 Vibe checkReviewed: 35 MDX files (8 with issues, 27 clean) + docs.json (navigation check) + Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: This is a large, well-structured PR — the guide pages (sales, marketing, CS, support, revops, SE) are some of the most consistently written content in the repo, and the Inventor and MCP pages are solid. The main drag is a handful of British spellings shared across the MCP page, claude-code, codex, and agent-skills files (looks like one example prompt that got copied four times), a title-case pattern in MCP frontmatter titles, and the conflicting install command identifiers in claude-code.mdx which is a real user-facing bug. The changelog's older entries (pre-May 2026) are full of banned words and marketing-style formatting, but those appear to be pre-existing content rather than new additions. 🔧 Issues (15)British spellings
The Heading/title case
Naming inconsistency
Technical correctness
Banned words in changelog (representative — many more instances exist in March 2026 and earlier entries which appear pre-existing)
🏗️ Page structure (1)
✅ Clean files (27)
🔋 Credit usage
Files read: |
🎯 Vibe checkReviewed: 35 MDX files (6 with issues, 29 clean)
Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: A large, well-executed PR — the vertical guide content (sales, CS, marketing, revops, SE, support) is some of the clearest role-targeted documentation in the repo, and the template is applied with impressive consistency. The MCP integration files carry a handful of British English slip-ins and one genuine cross-page technical contradiction on Codex setup commands that should be resolved before merge. 🔧 Issues (9)
🧩 Component suggestions (1)
|
| Item | Count |
|---|---|
| Files reviewed | 35 MDX |
| Context pages read | 0 additional (all changed files treated as primary; mcp-server.mdx and codex.mdx cross-checked against each other internally) |
| Total lines processed | ~5,900 |
Files read: build/invent/invent.mdx (241 lines), changelog.mdx (828 lines), get-started/core-concepts/mcp-plugins.mdx (213 lines), guides/customer-success/getting-started.mdx (187 lines), guides/customer-success/account-health.mdx (96 lines), guides/customer-success/qbr-prep.mdx (96 lines), guides/customer-success/renewal-expansion.mdx (96 lines), guides/customer-support/getting-started.mdx (187 lines), guides/customer-support/kb-generation.mdx (96 lines), guides/customer-support/response-drafting.mdx (96 lines), guides/customer-support/ticket-triage.mdx (96 lines), guides/marketing/getting-started.mdx (196 lines), guides/marketing/campaign-analytics.mdx (96 lines), guides/marketing/content-repurposing.mdx (96 lines), guides/marketing/lifecycle-campaigns.mdx (96 lines), guides/revops/getting-started.mdx (189 lines), guides/revops/data-dedup.mdx (96 lines), guides/revops/lead-routing.mdx (96 lines), guides/revops/pipeline-hygiene.mdx (96 lines), guides/sales/getting-started.mdx (196 lines), guides/sales/competitive-intelligence.mdx (96 lines), guides/sales/crm-data-enrichment.mdx (96 lines), guides/sales/lead-scoring.mdx (96 lines), guides/sales/meeting-briefs.mdx (96 lines), guides/sales/personalized-outbound.mdx (96 lines), guides/sales/prospect-research-use-case.mdx (105 lines), guides/solution-engineering/getting-started.mdx (196 lines), guides/solution-engineering/demo-prep.mdx (96 lines), guides/solution-engineering/discovery-summaries.mdx (96 lines), guides/solution-engineering/rfp-responses.mdx (96 lines), integrations/mcp/agent-skills.mdx (111 lines), integrations/mcp/claude-code.mdx (126 lines), integrations/mcp/codex.mdx (143 lines), integrations/mcp/mcp-client.mdx (94 lines), integrations/mcp/mcp-server.mdx (335 lines)
- Capitalize the product name 'MCP & Plugins' everywhere (headings, cards, links) - Capitalize product nouns (Agents, Tools, Workforces, Triggers) in mcp-plugins card titles - Sentence-case MCP page titles (Claude Code plugin, MCP server, MCP client, Agent skills) - Fix British spellings (behaviour, personalised, categorises, cancelled, labelled) - Standardize Claude Code plugin identifier on RelevanceAI/cc-plugin - Reconcile Codex setup commands in mcp-server.mdx with the dedicated Codex page - Convert the Agent MCP setup numbered list to <Steps> in mcp-client.mdx - Mention building via MCP & Plugins in the quick start - Fix Invent -> Inventor typo in invent.mdx Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVsFqM7fyBzhVdaQ5GWBMx
A leftover </content> closing tag at the end of mcp-plugins.mdx had no opening tag, causing the Mintlify deploy to fail with 'Unexpected closing slash in tag' — which is why the page did not render. Verified the file and all changed pages compile with the MDX parser. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVsFqM7fyBzhVdaQ5GWBMx
🎯 Vibe checkReviewed: 36 MDX files (5 with issues, 31 clean) + docs.json (navigation, no issues) + .github/workflows/vibe-check.yml (non-doc, no docs impact) Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: Genuinely strong PR. The six role-based guide sections (Sales, Marketing, RevOps, Customer Support, Customer Success, Solution Engineering) are well-crafted — consistent structure, good use of CardGroups, practical example prompts, no fluff. The MCP integration docs are clear and technically precise. The main drag is 🔧 Issues (10)Banned words in These appear in
Borderline banned word in new content
Technical accuracy
🧩 Component suggestions (2)
🏗️ Page structure (1)
✅ Clean files (31)
Non-doc files: 🔋 Credit usage
Files read: |
🎯 Vibe checkReviewed: 35 MDX files (11 with issues, 24 clean) + 2 non-doc files noted below Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: This is a well-executed, high-volume PR — 35 pages with tight, consistent structure and business-first writing throughout. The main problem is a single capitalization convention applied inconsistently: the same three errors repeat in all six "getting-started" pages, and 🔧 Issues (18)Product term: "Workforce" lowercase in headings (6 files)
Note: the body text immediately below each heading correctly uses Product term: "Knowledge" lowercase in headings and card titles (6 files × 2 locations)
Product term: "agent"/"tool" lowercase in
Product term: link text in
Product term: FAQ answer body
Product term: Step title
Banned word
🏗️ Page structure (1)
✅ Clean files (24)
Non-doc files: 🔋 Credit usage
Files read: |
3 participants
Rebrand the "Programmatic GTM" feature to "MCP & Plugins" across documentation and navigation to better reflect the broader scope of the Model Context Protocol integration.
Changes
get-started/core-concepts/programmatic-gtm.mdx→get-started/core-concepts/mcp-plugins.mdxintegrations/mcp/programmatic-gtm/tointegrations/mcp/(flattened hierarchy):claude-code.mdxcodex.mdxmcp-server.mdxagent-skills.mdxdocs.jsonto reflect new page paths and group titledocs.jsonto maintain backward compatibility with old URLsRationale
The rebrand clarifies that this is a Model Context Protocol integration feature applicable across use cases, not limited to go-to-market scenarios. The flattened directory structure improves navigation clarity.
https://claude.ai/code/session_01LVsFqM7fyBzhVdaQ5GWBMx