Skip to main content

MCP server

The Bryntum MCP server gives your agent live access to the official Bryntum documentation. Instead of relying on its training data — which is often outdated or invented — the agent can search the real docs for a specific product and version, and read a set of canonical setup guidelines.

It lives at:

https://mcp.bryntum.com

What it provides​

Once connected, the agent (the server identifies itself as bryntum-docs) gets one tool and four resources.

Tool — search_bryntum_docs​

Searches the official documentation for API references, configuration options, examples, and best practices. Parameters:

  • query (required) — a natural-language description of what you want to find.
  • product (optional) — gantt, scheduler, schedulerpro, grid, calendar, or taskboard.
  • version (optional) — the version from package.json, or latest.
  • limit (optional) — max results (default 10, max 100).

The Bryntum skill instructs the agent to call this whenever it's unsure about configuration, an API method, or an integration step.

Resources — setup guidelines​

The server also exposes four read-only MCP resources (Markdown) holding canonical, version-independent rules. MCP-aware agents can read these directly — no search query needed — to ground their setup before generating code:

ResourceURICovers
Setup guidelinesbryntum://guidelines/setupSetup and example rules; prefer docs/MCP over memory
CSS & theme rulesbryntum://guidelines/css-themesThe Bryntum 7+ three-part CSS import pattern and common mistakes
Framework integrationbryntum://guidelines/framework-integrationAngular / React / Vue idiomatic patterns and pitfalls
API & example safetybryntum://guidelines/api-safetyReferencing APIs and generating safe code examples

These overlap with the Bryntum skill and our common mistakes page — they're the same rules, served straight from Bryntum so they stay current.

Connect it​

Claude Code​

claude mcp add --transport http bryntum https://mcp.bryntum.com

Claude Desktop​

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "bryntum": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.bryntum.com"]
    }
  }
}

Cursor​

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "bryntum": {
      "url": "https://mcp.bryntum.com"
    }
  }
}

Other MCP clients​

Any MCP-capable client can connect over HTTP to https://mcp.bryntum.com, or via the mcp-remote npx bridge shown above for stdio-only clients.

How the agent should use it​

When searching, the agent should always pass a natural-language query, and scope it with product and version (from package.json) so results match the installed release. Before generating setup code, it's worth reading the guideline resources above first.

Prompt for your agent
Before writing any Bryntum code, use the Bryntum MCP server to look up the current config and API for the feature I asked about. Pass the product and the version from `package.json`. Don't guess config names from memory.

If the MCP server isn't available​

The skill includes a fallback: the agent should ask you to add the server, and in the meantime use WebFetch / WebSearch against bryntum.com:

  • API docs: https://bryntum.com/products/{product}/docs/api/
  • Guides: https://bryntum.com/products/{product}/docs/guide/

Connecting the MCP server is strongly preferred — it returns focused, version-correct results instead of whole HTML pages.