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. Say what you need

Ask for edits, publishing, or today’s and yesterday’s page views.

Instructions for your assistant

Help me use Kuura through this AI assistant. If I have not already said what I want to do, ask me, then guide me through setup in plain language. The same connection supports creating, editing and publishing websites, managing multiple sites, images, versions, add-ons, news, blogs, calendars and page-view queries.

Add the remote MCP server https://app.kuura.app/mcp (Streamable HTTP, browser-based OAuth and dynamic client registration). If a connection already exists, check it first. If you cannot add it yourself, guide me to the correct settings in this app. Do not claim the connection works before testing it.

Choose the permissions needed for my task: sites:read (reading websites), sites:write (editing), sites:create (creating), sites:publish (publishing), addons:read and addons:write (add-ons and content), and analytics:read (page views). Request contacts:read only if I need personal information in contact messages or bookings, and media:read only if I need my entire media library. Explain the required permissions in plain language; I approve the websites and permissions on Kuura’s page. Creating a website also requires access to my future websites. If a permission is missing later, help me reconnect with the permissions needed.

Open Kuura’s sign-in and consent page in English (ui_locales=en) so I can choose the websites and permissions. My email must be verified. Do not ask me to paste passwords, verification links or access tokens into chat.

Once connected, call kuura_account and kuura_list_sites, discover the available tools and read the kuura://guide resource. Help me choose the right website or create a new one. Use the appropriate Kuura tools for the task and follow their instructions. Fetch page views from the actual counter for the requested dates; do not invent numbers. If a feature is unsupported, explain that and guide me to Kuura’s own interface.

Read the current source before editing and preserve other pages and add-ons. Save source changes as a draft first and show what changed. Publish only at my request and with the granted permissions; Kuura packages and publishes the website. Follow the publishing job until it finishes and provide the working URL. Keep in mind that changes to dynamic add-ons and already published content may appear immediately. Do not make changes outside my request.

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.

Connection details and troubleshooting

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

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. Personal information in messages and bookings, and access to your entire media library, need separate permissions. 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 and sending customer messages are handled in Kuura’s own interface.

Open connection settings

MCP questions and answers

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.