
JointJS MCP Server
from archcore-ai
The JointJS MCP Server gives your AI coding assistant direct access to up-to-date JointJS documentation, API references, and working demo code.
Version: 4.2
On this page
The JointJS MCP Server gives your AI coding assistant direct access to up-to-date JointJS documentation, API references, and working demo code. Instead of relying on the AI's training data β which has a knowledge cut-off and may reflect outdated APIs β the server queries a continuously updated hybrid search index (semantic + keyword) built from the official JointJS documentation and demo repositories, optimised for accurate, LLM-friendly retrieval.
Why use it?β
-
Always current. Documentation is kept up-to-date in a dedicated index, so you get the latest API changes, deprecation notices, and migration guides β not a frozen snapshot from the model's training window.
-
Versioned. Every query can be scoped to a specific JointJS version, so the assistant gives answers that match the version you are actually using.
-
Reduces hallucination. The assistant grounds its answers in retrieved source text rather than recalling potentially incorrect training data about JointJS internals.
-
Demo-first workflow. Full, runnable demo projects are indexed and retrievable by framework (TypeScript, JavaScript, React, Angular), so you can paste working code directly into your project.
-
No setup cost. The server is hosted at
https://mcp.jointjs.com/mcpβ there is nothing to install or maintain on your end.
Toolsβ
The server exposes the tools listed below. The AI assistant invokes them automatically when it determines they are relevant, but you can also prompt it explicitly (e.g. "search the JointJS docs for...").
search_docsβ
Search JointJS documentation, API reference, guides, and migration notes using a natural-language query.
Parameter Type Required Description query string Yes Natural-language search query, e.g. "how to add a custom shape" version string No JointJS version to scope the search, e.g. "4.0". Omits to search the latest available version.
When to use: conceptual questions, API option semantics, compatibility guidance, migration notes, or any question whose answer is best found in prose documentation.
get_docβ
Retrieve the full Markdown content of a specific documentation page by its path.
Parameter Type Required Description path string Yes Internal path of the documentation page, e.g. "versioned_docs/version-4.0/intro/index.md". You typically obtain this value from search_docs results.
When to use: when search_docs returns a filename you want to read in full, or when you know the exact path of a documentation page.
search_demosβ
Search JointJS demo projects and example code using a natural-language query. Returns a ranked list of demos with demo_id values you can pass to get_demo_code. The AI assistant automatically selects and calls these tools when relevant. You can optionally guide it with prompts like: "Search JointJS demos for...".
Parameter Type Required Description query string Yes Natural-language search query, e.g. "drag and drop between containers" version string No JointJS version to scope the search, e.g. "4.2". Omits to search the latest version. framework string No Filter by framework: "ts" (TypeScript - vanilla), "js" (JavaScript - vanilla), "react", or "angular".
When to use: when you want a complete, runnable example or need to see how a feature is implemented end-to-end.
get_demo_codeβ
Retrieve all source files of a JointJS demo. Text files (.ts, .tsx, .js, .jsx, .json, .md, .css, .html) are returned inline; binary assets (fonts, images) are returned as GitHub links.
note
Very large demos may be truncated depending on the client's context limits.
Parameter Type Required Description demo_id string Yes Demo identifier returned by search_demos, e.g. "version-4.2/ai-agent-builder/js"
When to use: after search_demos identifies a relevant demo, call this tool to fetch its full source so the assistant can adapt it for your project.
list_doc_versionsβ
List all JointJS documentation versions available on the server.
Parameter Type Required Description (none) β β This tool takes no parameters.
When to use: to discover which version strings are valid for the version parameter of search_docs or search_demos.
Best practicesβ
- Ask specific, implementation-focused questions
"How do I add a collapsible minimap in my JointJS diagram?"
- Specify your JointJS version when relevant
"in JointJS 4.2"
- Ask for demos when building features
"Find a demo showing..."
- Combine docs + demos
"Explain how link validation works and show a demo"
Summaryβ
Benefit Detail No knowledge cut-off Documentation is served live from the official JointJS docs, so API changes released after the model's training date are always available. Version-accurate answers Scope any search to the exact JointJS version you are using β no more answers that silently mix APIs from different releases. Working demo code Full demo projects indexed by framework let you copy-paste real, tested code rather than relying on synthetic examples. Grounded responses The assistant cites retrieved documentation text, making it easier to verify answers and spot mistakes. Zero maintenance The server is hosted and updated by the JointJS team β you connect once and always get fresh content. Broad client support Works with Claude, Cursor, VS Code Copilot, OpenAI Codex, and any other MCP-compatible client via a single HTTPS endpoint.
Installationβ
The JointJS MCP server endpoint is:
https://mcp.jointjs.com/mcp
-
Claude Desktop
-
Claude Code (CLI)
-
Cursor
-
VS Code (Copilot)
-
OpenAI Codex / ChatGPT
-
Other clients
-
Open Settings β Connectors.
-
Click Add custom connector.
-
Enter
https://mcp.jointjs.com/mcp. -
Save/enable it.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under Apache-2.0β you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub β