Developer Tools
daypilot.org
Provides tools for discovering, generating, and resolving DayPilot Builder projects, components, themes, and packages for JavaScript frameworks.
ENDPOINT 1
https://mcp.daypilot.org/mcp
MCP server metadata
- Name
- daypilot
- Version
- 0.1.0
Use search to find official DayPilot references and fetch to read their published content. Preserve edition restrictions and cite canonical source URLs. These are current references; check installed package typings and runtime before assuming compatibility with an older release. A generic introduction build and current availability table do not establish per-edition historical support. A result with fetchSupported=false can be opened with a web client. Fetch continuation uses nextOffset and the returned revision. Use resolve_package for current official releases; preserve installed versions and licensed dependencies unless an upgrade is requested. Use theme_manifest before render_theme and pass its revision; apply returned CSS globally with the component theme prefix. For a deliberately new project use builder_catalog, validate_project, then generate_project with the same specification and returned digest. Download using its POST recipe, verify the archive SHA-256 before extracting into a new directory, and follow the generated README/AGENTS. Preserve existing applications; Builder does not patch or merge them.
Known tools 8
builder_catalogDiscover Builder components, targets, settings, option IDs and defaults for deliberately creating a new project.
Inferred read-onlyfetchRead the published DayPilot API/documentation/CODE article or JavaScript demo Markdown at a canonical source URL.
Inferred read-onlygenerate_projectGenerate and verify a new Builder project ZIP using the same validated specification plus expectedProjectDigest.
Inferred read-onlyrender_themeRender complete CSS from a current theme_manifest revision, a unique CSS prefix and optional property overrides.
Inferred read-onlyresolve_packageResolve the latest official DayPilot Lite or Pro release for JavaScript, React, Angular or Vue.
Inferred read-onlysearchSearch official DayPilot documentation, API references, examples and release information.
Inferred read-onlytheme_manifestDiscover supported theme settings, defaults and value domains for a DayPilot component.
Inferred read-onlyvalidate_projectPreflight a new Builder project using a discovered catalogRevision, component, edition, target, projectName and setting-ID to option-ID map ({} uses defaults).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.daypilot]
url = "https://mcp.daypilot.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"daypilot": {
"type": "http",
"url": "https://mcp.daypilot.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: daypilot
Remote MCP URL: https://mcp.daypilot.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"daypilot": {
"url": "https://mcp.daypilot.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"daypilot": {
"type": "http",
"url": "https://mcp.daypilot.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "daypilot",
"transport": "streamable-http",
"url": "https://mcp.daypilot.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.