@timelesscms-com/mcp-server 0.5.0 → 0.7.0

package/dist/tools/bulk.js

@@ -6,7 +6,7 @@ function v(version) {
 export const bulkTools = [
     {
         name: 'bulk_replace_text',
-        description: 'Replace a literal substring or regex across pages in one call. ALWAYS run with dry_run=true first and show the sample_diffs to the user before running the real call. Writes go through the normal pipeline (SEO transforms + revision snapshots).',
+        description: 'Replace a literal substring or regex across pages in one call. ALWAYS run with dry_run=true first and show the sample_diffs to the user before running the real call. Writes go through the normal pipeline (SEO transforms + revision snapshots). Response shape: { dry_run, updated, total_matches, pages_with_matches, sample_diffs_shown, additional_pages_with_matches, sample_diffs[], skipped (deprecated) }.',
         inputSchema: {
             pattern: z.string().min(1).describe('Literal substring (default) or JS regex source if regex=true.'),
             replacement: z.string(),

package/dist/tools/deploy.js

@@ -6,9 +6,10 @@ function v(version) {
 export const deployTools = [
     {
         name: 'trigger_deploy',
-        description: 'Enqueue a deploy of the currently active version. Returns a job_id immediately; poll get_deploy_status until the status leaves queued/running.',
+        description: "Enqueue a deploy of the currently active version. Returns a job_id immediately; poll get_deploy_status until the status leaves queued/running. With `dry_run: true`, the deploy runs through every step EXCEPT the hosting-adapter upload — useful for validating a structural change (new collection routes, schema bump, mode switch) without risking the live site. A dry_run job that succeeds proves the build is clean; one that fails returns the same astro stack-trace in get_deploy_status.error as a real deploy would.",
         inputSchema: {
             environment: z.enum(['production', 'staging']).optional(),
+            dry_run: z.boolean().optional().describe('Run the build but skip the CDN upload. The job ends in succeeded/failed the same way a real deploy does.'),
             version: versionParam,
         },
         handler: withErrorBoundary(async (args, { client, siteId }) => {
@@ -27,7 +28,7 @@ export const deployTools = [
     },
     {
         name: 'get_deploy_status',
-        description: 'Status of a single deploy job (queued | running | succeeded | failed).',
+        description: "Status of a single deploy job. Returns { job, queued_for_seconds, queue_timeout_seconds }. job.status is one of queued | running | succeeded | failed. Polling cadence: ~5s for queued/running. A job stuck in 'queued' for longer than queue_timeout_seconds (default 300s) auto-flips to failed with phase='queue_timeout' — so a single poll past that timestamp returns the terminal state and you can stop polling.",
         inputSchema: { job_id: z.string() },
         handler: withErrorBoundary(async (args, { client, siteId }) => {
             const res = await client.get(siteId, `deploys/${encodeURIComponent(args.job_id)}`);

package/dist/tools/sites.js

@@ -10,6 +10,14 @@ export const siteTools = [
             return ok(res);
         }),
     },
+    {
+        name: 'get_site_capabilities',
+        description: "Discover what the site-template renderer supports for this site. Returns a manifest of feature flags (blocks-mode, x-include, collection routes, custom block scripts, dry-run deploys, etc.) plus template_capabilities_version + the core block type ids. Call this when you're about to do something structural (set route_template on a collection, switch a page to blocks-mode, install a custom block type) and want to feature-detect rather than guess. The manifest is platform-wide today; per-site custom templates land later.",
+        handler: withErrorBoundary(async (_args, { client, siteId }) => {
+            const res = await client.get(siteId, 'capabilities');
+            return ok(res);
+        }),
+    },
     {
         name: 'update_site',
         description: 'Edit Site-level identity fields: name (display), slug (drives the {slug}.timelesscms-fallback subdomain — kebab-case, 3-48 chars, unique across the org), domain (the customer\'s real hostname; pass "" to clear). For colors / fonts / contact info / tagline use update_site_settings instead.',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timelesscms-com/mcp-server",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "Model Context Protocol server for the TimelessCMS public API. Use with Claude Code or any MCP-compatible client to manage a TimelessCMS site.",
   "license": "MIT",
   "type": "module",