Conversation
- new guide covering task hierarchy, projects, selection, and REST backend scenarios for the DHTMLX MCP server - setup instructions for Claude Code, Cursor, Antigravity, and ChatGPT - registered guides/mcp-server in the Guides sidebar category
- reworded title, description, and all six section headings that were duplicated (or near-duplicated) across other DHTMLX product MCP guides - reworded the intro's AI-failure-mode sentence and MCP-server-as- solution clause, and the "Where MCP helps"/"How it works" opening sentences, for the same reason - added a Search vs Inference workflow explanation to the "How it works" section - updated the ChatGPT setup section with the current OpenAI docs URL - 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 how_to_start.md and overview.md
- reworded RAG/MCP explanation for clarity - adjusted 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 Kanban, Spreadsheet, Diagram, Booking, and Pivot MCP guides - same links and facts, different sentence construction throughout
- reworded three prompts (indentTask, copyTask/pasteTask, setProject) that named the exact method matching the described goal, leaving nothing for the assistant to look up - prompts now describe the outcome and let the assistant find the right method
- reworded "Below are setup instructions for commonly used tools." which was copied verbatim across seven guides (Kanban, Spreadsheet, Todolist, Booking, Pivot, Vault, RichText)
- reworded the intro's second sentence in plain prose instead of raw identifiers (copyTask(), indentTask(), taskShape), keeping links to the same API pages - shifted the tone from a failure list (invents/misplaces/reaches for options that no longer exist) to a positive "getting the most from all that depth" framing, matching the warmer tone used in the RichText and Booking guides
- reworded the intro's second sentence so its closing device no
longer matches the "Getting the most out of/from X means Y"
skeleton that had converged across five sibling guides
- switched to a conditional ("If generated code is going to work,
it needs...") construction instead
- the intro sentence said "register the MCP endpoint" without explicitly connecting that to the URL shown in the code block right below it - reworded to "point your tool at the URL below" for a direct, unambiguous reference
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
- assistant now isolates only the doc-needing part of a compound prompt before querying MCP, handling the rest from its own knowledge - fixed intro referencing the example prompt before it was introduced - split the example-prompt sentence into its own paragraph - varied wording to avoid repeating the same verb in intro and step 1
- reworded example prompts to describe the desired behavior instead of naming the exact method/property upfront, so the walkthrough still demonstrates the value of the documentation lookup - applied the same fix to the how-it-works walkthrough prompt, which previously named RestDataProvider/event bus/api.setNext() directly - trimmed the closing sentence and the sample-prompts intro, both of which repeated wording already covered elsewhere in the guide
[add] MCP server guide for To Do List docs
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.