Skip to content
DayPilot

Official references and developer tools

DayPilot for AI-assisted development

Give your coding assistant access to DayPilot documentation, API details, package releases, CSS themes and project generation.

Connect your assistantExplore the tools

Connect to DayPilot MCP

Add the official DayPilot server to a coding assistant that supports remote MCP over Streamable HTTP. Public tools require no DayPilot account or license key.

https://mcp.daypilot.org/mcp

The connection guide includes setup commands for Codex and Claude Code. Your client controls tool permissions and access to your local project.

Work on an existing application

Start with your application's framework, component, edition and installed DayPilot version. Keep its dependencies and lockfiles unless you intend to upgrade.

Find the right API and example
search finds official references, demos and tutorials. fetch reads supported pages with their published code examples and edition notes. Check the installed TypeScript declarations when applying current documentation to an older version.
Choose a package
resolve_package returns the latest official Lite or Pro release for JavaScript, React, Angular or Vue, with installation and license guidance. It does not establish compatibility with an existing application or select historical versions.
Create a CSS theme
theme_manifest lists settings and defaults; render_theme generates complete CSS with a chosen prefix. Load the CSS in your application and set the component's theme property. Check your edition and installed version before using component features.

Start a new project

When you want a new scaffold, the MCP tools expose DayPilot UI Builder:

  1. builder_catalog discovers components, framework targets, settings and supported options for your edition.
  2. validate_project checks the selected configuration and release identity.
  3. generate_project returns a verified ZIP receipt and download instructions. Your assistant downloads the archive, checks its SHA-256 and extracts it into a new directory.

Generated projects include README and AGENTS instructions. Follow them to install dependencies, build and test the application. Generation does not run or validate application behavior. Builder covers a configurable subset of DayPilot; use the documentation and API reference for features beyond its catalog.

Use the tools over HTTP

The same operations are available through public JSON endpoints, so scripts and agents can use them without an MCP client. For example, read the current Builder component catalog:

curl https://mcp.daypilot.org/api/v1/builder/catalog

See the HTTP operations and parameters for retrieval, package resolution, theme rendering and project generation. The JavaScript agent index also links directly to component guides, installation sources and release demos.

Editions, versions and access

These tools support development with DayPilot for JavaScript and its framework integrations. DayPilot Lite uses the Apache License 2.0. DayPilot Pro requires a commercial license for production use; public Pro package instructions and generated starters use the evaluation trial. Preserve your existing licensed package when working on a licensed application.

Check the Lite/Pro feature matrix, each reference page's platform and edition notes, and your installed version. A current release, theme setting or example is not a promise of availability in every component, edition or historical version.

The DayPilot tools use public references and stateless theme/project generation. They cannot inspect your local files, execute your application or access private bookings or license keys. Your coding assistant applies changes locally; review and test the resulting application as you normally would.

Documentation · API reference · Support