Conversation
- new guide explaining the DHTMLX MCP server and how it serves live Kanban documentation to AI coding assistants - setup instructions for Claude Code, Cursor, Google Antigravity, ChatGPT, and other MCP-aware tools - example prompts for cards/columns, editor fields, toolbar, and REST/multiuser sync scenarios - registered the new page in sidebars.js - yarn.lock updated for transitive dependency bumps (chokidar, readdirp, sass, immutable, docusaurus-plugin-sass)
- emphasized workflow names for consistency with rest of doc
- reworded the title and H1 tail so they no longer match Spreadsheet and Todolist's near-identical "MCP server for AI tools/assistants" ending, which all three converged on after being reworded to lead with the keyword phrase for SEO
- changed the MCP endpoint block from a heading to bold text to avoid skipping a heading level (H1 straight to H4) - added inbound links to the guide from index.md, how_to_start.md, and howtos.md, since it previously had no discovery path outside the sidebar
- reworded RAG/MCP explanation for clarity - adjusted example and prompt-writing guidance wording
- reworded the Setup section's intro sentence, five tool-specific info boxes (Claude Code, Cursor, Antigravity 2.0, Antigravity CLI, ChatGPT), and the "Other tools" paragraph so they no longer read as verbatim-identical to the same content in the Spreadsheet, Todolist, Diagram, Booking, Pivot, and Vault MCP guides - same links and facts, different sentence construction throughout
- reworded "Below are setup instructions for commonly used tools." which was copied verbatim across seven guides (Kanban, Spreadsheet, Todolist, Booking, Pivot, Vault, RichText)
- the "Bind editor fields to card fields" heading had no explicit
anchor ID, so translated locales (de, ru, zh, ko) auto-generated
their own slug from the translated heading text instead of the
English one
- this broke the MCP server guide's link to this section in every
translated locale (confirmed via build)
- added {#bind-editor-fields-to-card-fields} to the heading in the
English source and all four translations, matching the existing
pattern already used on the neighboring "Configure editor behavior"
heading
- reworded the intro's first paragraph to describe cardShape, editorShape, the api parameter, and RestDataProvider in plain prose instead of raw identifiers, while keeping links to the same guide sections
- reworded the intro's second sentence from a failure-list framing (an outdated snapshot "leaves an AI assistant merging...folding... reaching for") to a plain "code holds up when it uses X, Y, Z" statement - this replaces an interim cleft-sentence version that made readers hold three list items in mind before reaching the payoff clause
- replaced "mutating" with "modifying" in the data API bullet for clearer, plainer wording - replaced "whatever the current API actually looks like" with "code that reflects the current API" for a less informal tone - reworded the Setup intro to explicitly point at "the URL below" instead of the vaguer "registers the same MCP endpoint"
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- the manual-setup step referenced "mcp.json" without the leading dot; Claude Code's actual project-scoped config file is .mcp.json
- merged numbered steps with the search/inference example into one walkthrough - unique wording to differentiate from other product guides
- corrected terminology (cards, not tasks) and pointed the example at RestDataProvider's automatic add-card sync instead of manual binding - assistant now isolates only the doc-needing part of a compound prompt before querying MCP, handling the rest from its own knowledge - split the example-prompt sentence into its own paragraph
- setup section opened with "Prefer the terminal or a config file?" - rephrased as a declarative statement
Add MCP server guide
- reworded intro sentence away from the "closes that gap... live line into" metaphor - reworded sample prompts to describe desired behavior instead of naming editorShape/cardShape, RestDataProvider, and getHandlers() directly, so the walkthrough still shows the value of the lookup
- "unlocks", "sharper", and the "under the hood" lead-in all replaced with plainer, shorter headings (each now under 40 characters)
- reworded the setup-section heading away from the "[verb]ing the MCP endpoint into your AI tool" template shared with Diagram/Spreadsheet/ Booking, and the prompts heading away from "Prompts to try" shared with Booking - trimmed the prompts-section intro, which repeated the same target-naming advice already covered by the first tip below it
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.
No description provided.