# Trainual ID: 11-trainual Page: https://gtmmcps.com/tools/11-trainual JSON: https://gtmmcps.com/data/tools/11-trainual.json Documentation references: https://gtmmcps.com/docs/11-trainual/ Category: Enablement & Coaching MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-02 Endpoint check: docs-only; date: 2026-09-04 SOP and process-documentation platform for onboarding and training, positioned more broadly at operations/HR than sales-specific enablement, with AI-assisted SOP drafting. ## MCP links - https://help.trainual.com/en/the-trainual-mcp-server - https://mcp.trainual.com ## Sources - https://trainual.com/pricing - https://operandio.com/trainual-pricing/ - https://github.com/trainual/tiptap-collaboration-mcp - https://trainual.com/product-updates/connect-trainual-integrations - https://help.trainual.com/en/the-trainual-mcp-server - https://zapier.com/mcp/trainual ## Research notes A public GitHub repo at github.com/trainual/tiptap-collaboration-mcp is real and maintained by Trainual's own GitHub org, but per its README it is an MCP server for Tiptap's collaboration/document service (Trainual's underlying editor infrastructure) - it does not expose Trainual's own product/training data. Do not cite it as a "Trainual product MCP"; mcp_status is none-found for Trainual-the-product on that basis. 2026-09-02: mcp_status none-found -> official. Trainual's own help center article https://help.trainual.com/en/the-trainual-mcp-server documents a remote MCP server at https://mcp.trainual.com, configured in Claude Desktop, Cursor or Windsurf with an Authorization: Bearer header, tokens created by Admin+ users, gated to the Premium and Enterprise plans; the 2026-07-14 product update https://trainual.com/product-updates/connect-trainual-integrations announces it ("Connect them to Trainual's Model Context Protocol (MCP) server"). Zapier and viaSocket also host third-party Trainual connectors (https://zapier.com/mcp/trainual: 5 triggers, 7 write actions), which are now secondary. trainual.com has no llms.txt and the official MCP registry has no trainual entry, which is why the 2026-08-24 pass found only the unrelated tiptap-collaboration-mcp repo; that caveat about the Tiptap repo still stands, but it no longer decides mcp_status. api_gate is left as recorded because it describes API access; the MCP plan gate is stated above. ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. - create-document: Create a new collaborative document; evidence: source; party: first-party - delete-document: Delete a collaborative document; evidence: source; party: first-party - duplicate-document: Duplicate a collaborative document; evidence: source; party: first-party - export-markdown: Export Tiptap JSON content to Markdown format; evidence: source; party: first-party - get-document: Get information about a collaborative document; evidence: source; party: first-party - get-document-statistics: Get real-time statistics for a specific document including current connections and connected IPs; evidence: source; party: first-party - get-server-statistics: Get server-wide statistics including total documents, connections, and usage metrics; evidence: source; party: first-party - import-markdown: Import Markdown content and convert to Tiptap JSON format; evidence: source; party: first-party - list-documents: List all collaboration documents; evidence: source; party: first-party - search-documents: Perform semantic search across documents; evidence: source; party: first-party - update-document: Update a collaborative document with new content; evidence: source; party: first-party ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.