@typeroll/mcp-server 0.7.8 → 0.7.9

package/AGENTS.md

@@ -33,9 +33,13 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
   - `html` — body lives in `html_content` as a single HTML string.
     Useful when you have hand-written markup to drop in directly.
 
-  Slug can contain slashes, so `2024/01/foo-bar` is a valid slug →
-  `/2024/01/foo-bar` URL. Encode hierarchy in the slug; the renderer
-  doesn't use `parent` for routing.
+  Slug is a single path segment — no slashes. `about` → `/about`,
+  `kontakt` → `/kontakt`, empty string `""` → homepage. The v1 API
+  rejects `services/design` and other slash-containing slugs with
+  "Invalid slug … slugs must not contain slashes." For nested URLs
+  like `/blog/{slug}` or `/services/{slug}`, the right primitive is a
+  **collection with `route_template`** (see the `tr-blog` and
+  `tr-directory` skills) — not a flat page with a slashed slug.
 
 - **Partials = global blocks.** Three kinds:
   - `header` — auto-injected at the top of every page.

package/dist/index.js

@@ -16,7 +16,7 @@ import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'
 import { TyperollClient } from './client.js';
 import { runInstallSkillsCli } from './install-skills.js';
 import { buildServer } from './server.js';
-const VERSION = '0.7.8';
+const VERSION = '0.7.9';
 async function resolveSiteId(client) {
     const fromEnv = process.env.TYPEROLL_SITE_ID?.trim();
     if (fromEnv)

package/dist/server.js

@@ -46,7 +46,7 @@ function effectFor(name) {
     }
     return 'write';
 }
-const DEFAULT_INFO = { name: 'typeroll', version: '0.7.8' };
+const DEFAULT_INFO = { name: 'typeroll', version: '0.7.9' };
 export function buildServer(options) {
     if (!options.fixedSiteId && !options.allowedSites) {
         throw new Error('buildServer: either fixedSiteId or allowedSites must be provided');

package/dist/tools/pages.js

@@ -65,11 +65,13 @@ export const pageTools = [
             'Slug is derived from the title when omitted. Default status is "draft". ' +
             'Homepage convention: pass slug="" (empty string) or omit slug and set title to "Home"; ' +
             'the server stores it under id "home" with slug "". ' +
-            'Do NOT pass slug="/"; strip leading slashes from slugs (use "about", not "/about"). ' +
+            'Slug must be a single path segment — no leading/trailing slashes, no internal slashes. ' +
+            'For nested URLs like /blog/{slug} or /services/{slug}, use a collection with a ' +
+            'route_template (see the tr-blog and tr-directory skills) — NOT a page slug with a slash. ' +
             'Returns the created page including html_content.',
         inputSchema: {
             title: z.string().min(1),
-            slug: z.string().optional().describe('URL slug without leading slash (e.g. "about", "services/design"). Empty string "" = homepage.'),
+            slug: z.string().optional().describe('URL slug — single path segment, no slashes (e.g. "about", "kontakt"). Empty string "" = homepage. For nested URLs use a collection with route_template, not a slug like "services/design" — the API rejects internal slashes.'),
             content_mode: z.enum(['blocks', 'html']).optional().describe('Default "html". "html" stores body in html_content; "blocks" stores a Block[] tree (note: blocks mode pages render as empty until the block editor ships — use html mode for all real content).'),
             html_content: z.string().optional().describe('Body HTML — only used when content_mode="html".'),
             blocks: z.array(z.any()).optional().describe('Block tree — only used when content_mode="blocks". Omit to get the default heading+prose seed.'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.7.8",
+  "version": "0.7.9",
   "description": "Model Context Protocol server for the Typeroll public API. Use with Claude Code or any MCP-compatible client to manage a Typeroll site.",
   "license": "MIT",
   "repository": {

package/skills/tr-blog.md

@@ -154,7 +154,7 @@ Three calls. No per-article `create_page`. No HTML diffing by hand.
 
 ## Pitfalls
 
-- **Don't fall back to "one page per article".** That was the pre-`item_template_html` pattern. It works but it's strictly worse: design changes mean editing N pages, you lose `{{url}}` resolution in listings, sitemap doesn't include items, and previews can't surface a per-item URL. If you find yourself writing `create_page` with `slug: "blog/foo"`, stop and reconsider — the only legitimate reason is a one-off "about the editorial team" page that isn't an article.
+- **Don't fall back to "one page per article".** That was the pre-`item_template_html` pattern. It's strictly worse now: design changes mean editing N pages, you lose `{{url}}` resolution in listings, sitemap doesn't include items, previews can't surface a per-item URL — and the API will reject your attempt anyway. `create_page` rejects slugs containing slashes ("Invalid slug … slugs must not contain slashes"), so `slug: "blog/foo"` doesn't even get through. The collection's `route_template` is the only path to nested URLs.
 - **Slugs must be unique within the collection.** `regenerate_collection_listing` will silently drop items where `slug` is missing; the listing count will be lower than the item count.
 - **Don't use non-ASCII field names.** `datum` not `Datum`; `forfattare` not `författare` in the `name`. The `label` is free-form.
 - **Listing goes stale if you forget step 4.** Every item change needs `regenerate_collection_listing`. Add it to your mental checklist after every `create/update_collection_item`.