UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Integrations

Claude Code

Use Ulika with Claude Code. Ask it to connect your site, or register the Ulika MCP server so it can scan content and customise code with structured tools.

Last updated October 14, 2026

Claude Code is Anthropic's terminal coding agent. In Ulika's integrations list it is described as "The terminal coding agent used to build and extend this project's codebase." Ulika works with it in two ways: Claude Code can simply run the Ulika CLI in its terminal, or you can register Ulika's MCP server so it gets structured tools.

In the Integrations list, the Claude Code row shows Connected only when the project was recorded as built with Claude Code. Otherwise it shows a Connect button, which only explains that Claude Code "is not connectable yet": there is nothing to connect from Ulika's side, because Claude Code runs on your computer. Use one of the two options below.

Option 1: just ask#

Claude Code has a terminal, so it can run the CLI itself. In the folder of your project, say:

Connect my site to Ulika.

The command it needs is ulika connect https://your-site.com. Ulika's connect screens show that sentence beside the exact command, so if Claude Code does not know it, paste it in. It shows you one approval link and code and waits while you approve once in the browser, then reports which sites are live, with editor links, and what needs you. Nothing needs to be registered or installed first. The full flow, the limits and the guard rails are in Connect with an AI agent.

If you do not give it an address, it should ask which website to connect. Ulika refuses its own address and repository, so it cannot connect the wrong site by accident. With the MCP server registered (below), the agent is also told never to ask you for a project name, a repository or a token.

Option 2: register the MCP server#

In your project, open Settings, then Integrations, and click Set up on Model Context Protocol. The first block, Claude Code, holds the command below for your Ulika address, with a Copy the Claude Code command button. See MCP tools for the whole panel.

Registering gives Claude Code structured results (JSON) instead of terminal text, and the code tools described below. Use Claude Code's own command:

bash
claude mcp add ulika -- npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz mcp

Everything after -- is the command Claude Code starts. Variations:

  • Unattended connect_site. Give the server a workspace token so it never needs a browser step: claude mcp add --env ULIKA_TOKEN=ovl_wt_xxx ulika -- npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz mcp. Keep that token secret; it is a credential for your workspace.

  • Another Ulika instance. claude mcp add --env ULIKA_SERVER=https://your-ulika-host ulika -- npx ... (same command, one more --env).

There is no Ulika-specific installer for Claude Code (the ulika codex install command is for Codex only), and Ulika does not write a Claude Code skill. The MCP server's own instructions tell Claude Code how to use the tools.

After registering, start Claude Code in your website's repository and ask the same sentence as above. It can now call tools such as connect_site, connect_sites, batch_status, scan_site and connection_status. Every tool, with its inputs and outputs, is documented in MCP tools.

Customising code with Claude Code#

When you ask Claude Code to change your website's code, the Ulika code tools (list_code_files, read_code_file, write_code_file) give it a guarded way to do it:

  • It must read a file first and pass that file's revision hash when writing, so it cannot overwrite a change made in the meantime.

  • Changes are saved as local drafts in your working tree. The tools never commit, deploy or publish; you review and ship the change with your normal Git workflow.

  • Hidden files, .env files, package.json and lock files, dependencies and build output are blocked.

  • The tools only work inside the folder Claude Code was started in when it launched the MCP server, so start it from the repository you want customised.

Content, meaning the words and images people edit in the visual editor, is changed in Ulika's editor, not by rewriting copy in components.

Good to know#

  • You approve once per computer. The approval lasts up to 30 days, or 14 days without use, and is limited to 50 sites in any rolling 24 hours. You can revoke it under Agents in your workspace settings.

  • For repositories owned by a GitHub organisation, you approve again every seven days.

  • The scan and any code editing stay on your computer; only the derived content manifest is ever sent to Ulika.

If something fails, see CLI errors and exit codes. Other agents: Codex and any MCP agent.

The claude mcp add options and scopes belong to Claude Code, not to Ulika, and can change between its releases. See Claude Code's MCP documentation for the current syntax.

Was this page helpful?

PreviousNetlifyNext Codex

On this page

  • Option 1: just ask
  • Option 2: register the MCP server
  • Customising code with Claude Code
  • Good to know
Ulika documentationFAQ · CLI reference · Terms · Privacy