MCP

​

Introduction

​

Generate a Token

1. Sign in to the backend and open the username dropdown at the top right.
2. Click MCP Tokens, then Generate Token.
3. Enter a Name that says where the token will be used, for example “Laptop Claude Code”.
4. Choose when the token Expires. The default is 90 days. Choose Never only for unattended service accounts.
5. Under Allowed tools, every read tool is checked. Clear the tools this token must not call. A token with every read tool checked also gains read tools added in later releases. Content tools are labeled (changes content) and are never checked by default. Check each content tool that this token needs. A token never gains a content tool unless you check it.
6. Click Generate.

​

Connect a Client

Authorization: Bearer cmcp_...

claude mcp add --transport http curator https://your-site.example.com/curator/mcp \
  --header "Authorization: Bearer cmcp_..."

​

Manage Tokens

​

Tools

​

Read and Administrative Tools

    {
        "total": 42,
        "offset": 0,
        "count": 2,
        "items": [
            {
                "id": 7,
                "title": "Sales Overview",
                "slug": "sales-overview",
                "url": "https://your-site.example.com/dashboard/sales-overview",
                "updated_at": "2026-09-01 14:02:11",
                "project_name": "Finance"
            }
        ]
    }

​

Content Tools

​

Safety Rules

• Managed and distributed portals refuse changes. On a portal that Central Dispatch manages, and on a high availability node, every content tool returns an error, but the read tools still work. On a managed portal, make the change on the managing Curator. On a high availability node, make the change in the Curator backend.
• New pages start hidden. A new page is hidden unless the client passes hidden: false. Publish a page with update_page_settings and hidden: false after you review it.
• Group restrictions are not set. No tool sets or edits the group restrictions on pages, menu items, or files. A page that a tool creates has no group restrictions. Check its restrictions in the backend before you publish it. A page that a tool recreates after a delete is hidden, and it is restricted to no groups, so no frontend user can open it until an administrator assigns its groups in the backend.
• Page text cannot contain code. Curator refuses rich text that contains scripts, event handler attributes, javascript: URLs, embedded frames, forms, style tags, or Twig tags. The same rule applies to hero headings, hero descriptions, and the descriptions of pages, files, and menu items, because Curator shows them as HTML. Links can use http, https, mailto, tel, sms, webcal, msteams, slack, and zoommtg addresses, relative addresses, and image data. To embed another site, use an iframe element.
• Theme styles cannot read server files. In custom CSS, update_theme accepts only one kind of @import: a remote stylesheet such as a web font, written as @import url('https://...');. It refuses other imports and the LESS functions that read files, such as data-uri(). When the styles do not compile, the error gives the line and column only.
• Some content is protected. No tool can change the theme’s head insert. The tools can add and edit only the common page elements. Other elements, such as accordions, tabbed pages, feeds, and lists, can be moved or removed, but not edited.
• Uploads are checked. Curator refuses file types that a web server can run as code. HTML, SVG, XML, and JavaScript files uploaded through MCP are saved as downloads only. Curator also checks the contents, so an HTML file with a name such as report.txt is saved as a download only too. set_theme_image accepts only raster images, such as PNG, JPEG, GIF, WebP, and ICO files, and refuses files that are downloads only, so an SVG logo or favicon can only be set in the backend. When a page embeds one of these HTML files, Curator renders it in a sandboxed frame.
• Deletes are checked. delete_page refuses the homepage and any page that another page embeds. It also refuses a page that a tabbed pages element, a tile selection, or a theme footer uses, unless the client passes force. It refuses a page that menu items link to, unless the client passes remove_menu_links, which deletes those menu items too. It always refuses when a linked menu item has children. delete_file refuses a file that pages or menu items use, unless the client passes force. delete_menu_item refuses an item that has children, unless the client passes include_children. No tool deletes or moves a top-level menu.

​

Undo Changes

​

Upload Large Files

​

Limits and Logging

• Requests are rate limited per client address using the same limits as the REST API, set under Settings > Security > Authentication Settings.
• Every tool call writes a Usage Log row of type interworks.portal.mcp.call with the tool, its arguments, the owner, the token prefix, and the outcome.
• Rejected sign-ins are written to the Curator log with the reason and the token prefix. The full token is never logged.