Lidarc
DE Sign in Request access code
Product Live demo Developers Templates Blog Sign in Request access code
Back to the home page
For developers

Connect your agent to any Lidarc site.

Every site has its own MCP endpoint. Your agent works with the same building blocks people use in the admin, and every input is validated.

Pick a theme
theme_activate
Set a look
design_set
Create a page
pages_create
Publish
pages_publish
Links into the admin
site_info

Connect

Every site’s endpoint is:

POST https://<your-site>/mcp
Authorization: Bearer <API key>

You create the API key yourself: in the admin under “Agents” or in your account with “Connect agent”. You choose the role, see the key once and can revoke it at any time. With Claude Code you connect like this:

claude mcp add --transport http lidarc https://<your-site>/mcp \
  --header "Authorization: Bearer <API key>"

Other MCP clients need the same two things: the address and the header. The endpoint follows the MCP specification (revision 2026-07-28) and still serves clients that open with the earlier handshake.

Tools

The tools follow your site: 16 apply to the whole site, plus 7 per collection. A site with pages and posts offers 30 tools. With Luna or Orbit, the header and footer are a collection of their own (layout), which makes 37.

Area Tools
Start site_info – instructions, links into the admin, release status
Theme and blocks themes_list, theme_activate, blocks_list
Composing pages page_guide (rules and a starting scaffold per kind of site), page_check (checks a page against the rules), page_variations (picks blocks to swap for others of the same kind)
Design design_get, design_set (single values, a whole look or a style)
Settings and menus settings_update, menu_get, menu_set
Media and clean-up media_list, demo_remove (moves example content to the trash)
Viewing and going live page_render (see a page in a browser, with findings and pictures), site_render (re-render the site)
Per collection <collection>_list, _get, _create, _update, _publish, _unpublish, _trash (e.g. pages_create, posts_publish)

The agent writes rich text as simple Markdown: **bold**, *italic*, links and lists.

An agent’s changes go online as soon as someone on your team releases them in the admin. A key that may publish can also re-render the site itself (site_render).

Validated input

Every block is checked against the active theme’s fields before anything is saved. If a required field is missing, the agent gets an error it can act on:

{ "isError": true,
  "structuredContent": { "message": "content[0] (hero).title: required" } }

Unknown blocks, invalid choices and unsafe image URLs are rejected the same way.

Roles

When you create a key, you pick one of three roles:

Role Can
Drafts only (recommended) create and edit content, not publish
Drafts and publishing also publish and re-render the site (site_render)
Build the whole site also theme, design, menus and settings

Example prompts

  • New site: “Call site_info. Build a site for a yoga studio in Bern: a fitting theme, the ‘Natur’ look, home, classes, contact. Send me the links into the admin at the end.”
  • Post as draft: “Write a blog post about our new opening hours. Draft only, don’t publish.”
  • Switch look: “Try the ‘Editorial’ look and give me the link to the page builder.”
  • Rework the menu: “Read the main menu with menu_get and reorder it: Offer, About, Blog, Contact.”

One call with curl

curl -X POST https://<your-site>/mcp \
  -H "Authorization: Bearer <API key>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"design_set","arguments":{"look":"handwerk"}}}'

Response with the Luna theme (shortened):

{ "ignored": [],
  "values": { "--ed-primary": { "light": "#9a3412", "dark": "#f2994a" },
              "--ed-font-display": "besley", "--ed-font-sans": "libre-franklin" } }

What’s still coming

  • Uploading media over MCP: soon. Today the agent passes images as URLs or uses the media library.
  • Design changes take effect immediately and are not drafts yet.
  • Approval list and activity log for agents in the admin: soon.
For agents & developers

Tools instead of prompt magic.

MCP · HTTP
site_info
Instructions, tools, blocks, links into the admin
pages_create
Create a page as a draft, blocks included
pages_update
Change a page's texts and blocks, as a draft
blocks_list
Approved blocks with their fields
media_list
Find images in the media library
menu_set
Set the navigation (admin key)
pages_publish · role
Publish, if the key is allowed to
→ pages_updatePOST
{
  "id": "01JC8QX4…",
  "data": {
    "content": [
      { "_type": "hero", "title": "Visitor Center" },
      { "_type": "cmp_hours_location",
        "title": "Opening hours",
        "hours": "Wed–Fri 13:00–18:00\nSat 10:00–16:00",
        "hours_note": "Guided tours Wed–Fri 15:00, Sat 11:00 and 14:00" }
    ]
  }
}
← pages_update200 OK
{
  "id": "01JC8QX4…",
  "slug": "visitor-center",
  "status": "draft",
  "url": "/visitor-center",
  "reviewInAdmin": "/_emdash/admin/content/pages/01JC8QX4…",
  "editInPageBuilder": "/_emdash/renderer/builder.html?page=01JC8QX4…"
}
With a key in the “Drafts only” role, every call lands in the CMS as a draft. Your team sees what the agent did before it goes live.
$ claude mcp add --transport http lidarc https://<your-site>/mcp --header "Authorization: Bearer <API key>"

> Build the Visitor Center page for Orbitwerk with the opening hours. Follow the rules from site_info: approved blocks only, everything as a draft.
# site_info (excerpt)
Tools: site_info · pages_list · pages_create · pages_update · blocks_list · page_guide · page_check · media_list · menu_set · design_set · pages_publish (role)
Blocks: depending on theme and library, see blocks_list
Rules: always create pages as draft · no free HTML · publish only with the role
Look: design_set, admin key only