KUURA + MCP

Connect your own AI assistant to your Kuura websites

Tell your assistant what to change, ask for a new website or check your page views. An MCP connection lets your assistant do these things in Kuura within the permissions you grant. Kuura saves versions, packages the pages and handles publishing.

Copy the setup instructions Manage your connections

What is MCP and what is it used for?

MCP, short for Model Context Protocol, is a shared way to connect an AI assistant to other services. It lets the assistant retrieve information and use permitted service features alongside the conversation. In Kuura, that means reading, editing and publishing your websites, working with add-ons and checking page views.

Your assistant sends changes to Kuura. Your websites stay in Kuura and publishing runs through Kuura, just as it does after editing the source in the browser editor.

Copy the instructions and let your assistant help

These instructions are public. You do not need to sign in to read or copy them. You approve access later on Kuura’s own page.

1. Copy the instructions

Paste the instructions below into your AI assistant. You can read and copy them without signing in.

2. Approve in Kuura

3. Test the connection

Ask your assistant to test account details, the website list and reading the guide. Continue your task once the required calls succeed.

Include your task in the same message as the instructions. Default permissions let you read analytics and edit and publish your selected websites. You can also choose a viewing-only connection on the consent page.

An edit is first saved as a draft that you can preview. To make the change visible on your site too, ask for example: “Make a test edit and publish it.” Publication is queued and usually finishes in about 10 seconds to 1 minute; it can take longer when the queue is busy. The assistant follows its progress and confirms when the change is published.

We recommend a quick Analyzer check after edits and before publishing. For example: “Check all my website links and basic SEO. Report broken links and anything left unverified.” Checks only need website read access and do not use AI credits. After publishing, also check public HTTP availability.

Instructions for your assistant

Help me use Kuura. Ask in one message only for missing details: the task, website and, if needed, date range. Use answers I have already given. Follow these steps:

1. Check for available Kuura tools. If present, go to step 5. Otherwise check this assistant’s MCP settings. Server: https://app.kuura.app/mcp (Streamable HTTP, OAuth, dynamic client registration). For Codex CLI in the same environment: codex mcp list; add only a missing connection with codex mcp add kuura --url https://app.kuura.app/mcp. If you cannot manage this assistant’s settings, guide the user to them. Consult further documentation only for missing information or a specific error.

2. Start one OAuth sign-in. The add command may already start it; do not run login alongside it. For an existing connection, use codex mcp login kuura (or its saved name) when sign-in is needed. Use the browser that opens automatically and the same tab; if it does not open, open the current pending request’s link once. Choose English on Kuura’s page (ui_locales=en). I sign in and approve the selections. Do not open another consent flow in a second browser.

3. By default, request all Kuura permissions so the same connection can read analytics, edit and publish websites, and access add-ons and personal information, read the media library and add images to it (media:read and media:write). Do not automatically restrict the connection to read-only access because the first task asks for analytics. I select the websites and approve the visible permissions on Kuura’s form. Creating websites also requires access to all my current and future websites; do not select that automatically. Only if I want a viewing-only connection, select sites:read and analytics:read.

4. After OAuth, check kuura_account: connection_id and scopes. Editing needs sites:write; publishing needs sites:publish. Uploading to the media library needs media:write. If permissions needed for the task are missing and have not yet been approved, request one new approval with the required permissions. If a new approval already exists but kuura_account returns the old connection_id, this session is using the old connection. Refresh this assistant’s MCP connection once if available. If the new connection or its tools still do not load, request an assistant or IDE extension restart and give a continuation message for the task. Describe the exact situation; do not say all tools are missing if reading works. End this attempt here; do not repeat consent or log out as an experiment.

5. Call kuura_account and kuura_list_sites, and read kuura://guide as an MCP resource. Briefly report the three results and check the task’s permissions; if missing, follow step 4. Check site_ids and all_own_sites: [64] means one website with ID 64. Match the website by name and follow next_after_id pagination as needed. An ambiguous display alone does not establish excessive access. Do not revoke connections as a troubleshooting experiment.

6. Continue directly with my task. For “all” page views, use kuura_get_analytics(site_id, period="all"): report the recorded daily-history total, counter and available date range; do not invent missing numbers. For edits, read the current source, preserve other content and save a draft. For MVC, use site_files.site_kind="mvc_multi_page", a shared layout_html and pages[].content_html. In the layout, <rime-content></rime-content> inserts the page content, <rime-title></rime-title> the title, <rime-description></rime-description> the description and <rime-navigation></rime-navigation> the links from navigation. See kuura://guide and the kuura_save_source schema for the complete structure. After a successful save, say “The change is done and saved as a draft” and provide the preview link. Saving alone does not queue publication; the site’s deploy_status=pending does not mean the save failed or prove that publication is queued. Publish only at my request and with granted permissions. If I asked you to edit and publish, continue with kuura_publish without asking for permission again. Say “The change is saved; publication is queued and usually finishes in about 10 seconds to 1 minute.” Poll kuura_get_job(site_id, job_id) about every 10 seconds until success, failed or cancelled; do not stop at pending. If it takes longer than a minute, explain the delay and keep checking; do not queue publication again. Only on success, confirm “The change is done and published” and provide the site link. If you cannot continue checking, report the last confirmed status and job ID. Images: kuura_upload_image adds a website attachment; kuura_upload_media adds to the personal media library and returns an immediately public image link. Accepted formats are JPEG, PNG and WebP, up to 2 MiB, 8 megapixels and 8192 px on either side; SVG and other files are rejected. Dynamic content changes may appear immediately. Do not ask for passwords or tokens in chat.

Recommended quick check: run kuura_analyze_site for the saved version_id after edits and before publishing. Check all pages, internal links, anchors, placeholders and basic SEO. Checks do not edit, publish or use AI credits. After publishing, run kuura_check_links with the same version_id and check_http=true to verify public HTTP availability too. Continue using next_after_link as after_link with the same version and filters until next_after_link=null. Combine every batch and report broken and unverified links. skipped, unchecked or scan_truncated do not establish that all links work. JavaScript links, forms, mailto/tel destinations and external anchors are not verified.

Your assistant must support remote MCP and OAuth sign-in. If a connection cannot be added in chat, your assistant can help with the app’s settings. Pasting the instructions alone does not grant access to your websites.

Quick link and SEO check

Quick check instructions for your assistant

Recommended quick check: run kuura_analyze_site for the saved version_id after edits and before publishing. Check all pages, internal links, anchors, placeholders and basic SEO. Checks do not edit, publish or use AI credits. After publishing, run kuura_check_links with the same version_id and check_http=true to verify public HTTP availability too. Continue using next_after_link as after_link with the same version and filters until next_after_link=null. Combine every batch and report broken and unverified links. skipped, unchecked or scan_truncated do not establish that all links work. JavaScript links, forms, mailto/tel destinations and external anchors are not verified.

Test an existing connection

Connection test for your assistant

Test the current Kuura connection: call kuura_account and kuura_list_sites, and read kuura://guide. Report each separately. Show connection_id, scopes, site restrictions and the task’s website. Check sites:write for editing and sites:publish for publishing. If permissions have not been approved, request approval once. If they are already approved on a new connection but kuura_account shows the old connection, refresh the assistant’s MCP connection; if needed, request a restart and give a task continuation message. Restarting alone does not grant permissions. If read tools work, say so. Do not repeat sign-in or revoke the connection as an experiment. Do not ask for credentials in chat.

Connection details and troubleshooting

Server address: https://app.kuura.app/mcp
Transport: Streamable HTTP. Sign-in: OAuth in your browser, with dynamic client registration.

Approve the connection in the browser that opens automatically. One sign-in attempt and one consent tab are enough. Leave any unnecessary permissions unchecked on Kuura’s page, even if the app requests them.

If only reading works, check the connection’s permissions. Editing needs sites:write; publishing needs sites:publish. Uploading to the media library needs media:write. If you already approved a new connection but the assistant shows the old connection number, refresh its MCP connection. A restart is needed only if the new connection or its tools cannot otherwise load. Restarting does not grant permissions.

The permission selection form opens through sign-in started by your assistant. Kuura’s connection page shows existing approvals. Website ID #64 refers to one website; the website count is shown separately.

If a website is missing or permissions are insufficient, reconnect and approve the sites and permissions you need. Creating new websites also requires access to your future websites. A connection lasts up to 30 days.

The instructions contain no passwords or access tokens. The default package also includes personal information in contact messages and bookings for selected websites, and your entire personal media library. All permissions are shown on the consent page and can be unchecked. You can revoke connections in Kuura.

What can you do with Kuura MCP?

Multiple websites, one assistant

Choose a website or create a new one. Edit a single page, a multi-page site or a shared MVC layout.

“Add a new services page to my business website.”

Source code, images and versions

Edit HTML, CSS and JavaScript, upload images and save drafts. Restore an earlier version as a new draft when needed.

“Change the homepage heading and keep the rest of the design.”

Content and add-ons

Create news and blog posts, change supported add-on settings and update weekly calendar availability.

“Add a news post about next week’s event.”

Page views and publishing

Fetch daily page views from your existing counter. Ask to publish the version you reviewed and follow its progress.

“How many page views did I get today and yesterday?”

You choose the permissions

Connecting requires your own Kuura account and a verified email. You choose the websites and whether the assistant may only read information, edit drafts or also publish. Enter your password on Kuura’s sign-in page, not in the assistant’s chat.

Personal data in contact messages and bookings, and access to your entire media library, require separate permissions. Billing, domain orders, DNS, permanent deletion of an entire website and sending customer messages are handled in Kuura’s own interface.

Open connection settings

Published content supports assistants too

Public, indexable pages published with Kuura hosting get Markdown text versions, a content index and discovery links. Assistants can read public content without an MCP connection. The MCP connection described here is a separate way to manage your own websites with the permissions you approve.

See agent-ready support and published website test results

MCP questions and answers

Can I use MCP with Hosting?

Yes. Hosting costs €4.99/month + Finnish VAT 25.5% (€6.26/month) and includes connecting your own domain. It adds no monthly AI credits. Build with starter credits or your own assistant through MCP. MCP source editing and publishing do not consume Kuura AI credits. Your assistant may have fees set by its provider. Domain registration and annual fees are separate.

Do I have to use MCP?

No. MCP is an optional way to use Kuura. You can create, edit and publish your websites directly in Kuura’s browser interface and use its built-in AI features without connecting an external assistant.

Do I need to sign in to read the instructions?

No. This page and the copyable instructions are public. Sign-in and a verified email are required only when you approve an assistant’s access to your websites.

Which assistants work with Kuura?

Your assistant must support remote MCP servers (Streamable HTTP), browser-based OAuth and dynamic client registration. Copy the instructions above into your app. If it cannot add a connection itself, the assistant can guide you through the settings. Support depends on the app you use.

Does the assistant publish changes immediately?

Saving source code creates a new draft version. Publishing is a separate action that requires publishing permission. Ask the assistant to show changes for review first. Changes to dynamic add-ons and already published news or blog posts may appear immediately.

Can I limit or revoke access?

Yes. You choose your own websites and permissions during approval. Reading personal data and your entire media library requires separate permissions. You can revoke access on Kuura’s AI assistants page. Publishing jobs already in the queue may still finish normally.