Getting started

The whole path: sign up, create a project, start your free trial, define what can be edited, add content, get an API token, and read it from your site. About ten minutes.

Two roles to keep in mind as you read:

  • You, the builder - you set the project up once.
  • Your editor - the non-technical person who keeps the content current. They only ever see the admin; none of the steps below are theirs.

1. Sign up

Go to kuracms.com and sign in. kura uses a magic link: enter your email, click the link we send, and you're in. No password to set.

2. Create a project

A project is one site's content. Create one and give it a name; kura derives a slug from the name (a short URL-safe id like riko-realty) that you'll use in the API and the MCP setup. The slug is shown on the project page at /app/{slug} ("Your project slug is ...").

3. Start your free trial

Add a card to start the project. The first month is free - you are not charged during it, and if you cancel inside the month you pay nothing.

Important: the trial (or a paid subscription) must be active for the public API to serve your content. A brand-new project starts on the free tier, which is not active, so the public REST API returns 402 Subscription inactive until you start the trial (checkout flips the project to active; the 30-day trial counts as active). A lapsed or paused project returns 402 too. Start the trial before you wire your site up, or the API serves nothing.

4. Define what can be edited (the schema)

Your schema is the set of content types and fields your editor will fill in. A property site might have a Listing type with fields for title, price, bedrooms, photos, and location.

Two ways to define it:

  • By talking to your AI coding tool - the fastest path. See Set up with your AI tool (MCP): say "add a bedrooms field to Listing" and the field, plus the editor form for it, appear.
  • In the admin - add content types and fields by hand from the project's admin UI.

One thing to know now: in v0.1 the schema is additive. You can add content types and fields, but you cannot rename or delete them yet. Name things the way you want them before you build a lot of content on top.

5. Add some content

Open the project admin, pick a content type, and create an entry. This is exactly what your editor will do day to day - a clean form, only the fields you defined, nothing else. Save it as a draft, then publish when it's ready. Only published content is served by the public API (add ?preview to a read to see drafts - see the REST API reference).

6. Get an API token

Your frontend reads content with a project token (prefixed kr_live_). On your project page at /app/{slug}, expand the Developer section and click Create token, give it a name (e.g. "Website"), and copy it - the token is shown once, so copy it immediately. You'll send it as a Bearer token on every API request. The token is full-access (it can write as well as read), so keep it server-side, not in client-side code.

7. Connect your site

Read your published content over HTTP:

GET https://kuracms.com/api/v1/{project}/{type}
Authorization: Bearer kr_live_your_token

You get clean JSON back, cached at the edge. Full details - filtering, sorting, pagination, and the exact response shape - are in the REST API reference. For a site you already have, see Connect your existing site.

That's the whole loop: define the shape, your editor fills it in, your site reads it. From here, set up the MCP server so your AI tool can manage the schema for you.