Skip to main content

Your own AI agent (MCP)

You can work on your sites with your own AI agent, such as Claude or ChatGPT. The agent connects to Kamu.build over MCP at https://mcp.kamu.build. It can read and edit sites, write blog posts, publish, start new sites, and create and edit your team's documents.

Kamu, the built-in agent, still works in the dashboard and on WhatsApp. You only need MCP if you want to use another agent.

The steps for Claude, ChatGPT and Claude Code are on Connecting an agent. Documents have their own page: Documents over MCP.

What the agent can access​

When you create a connection, you choose what the agent can access:

  • Whole team. All of the team's sites and the team's documents. Sites the team gets later are included too. This option is for team members
  • Chosen sites. Only the chosen sites, no documents. This suits, for example, an agency that has been invited to one site

A user who has been invited only to a site and is not a team member can only choose sites. The approval page has a link for creating a team of their own.

You do not need an account beforehand. If you have none, connecting creates an account and a team. See Connecting an agent.

What the agent can do​

The connection gets one level. Edit is selected by default.

LevelWhat it allows
ReadSite details, files, visitor statistics, publishing history and blog posts. The team's documents and their content
EditAs Read, plus editing site content, writing blog drafts, and creating and editing documents. With a Whole team connection also creating a new trial site. Nothing is visible to visitors yet
Edit and publishAs Edit, plus publishing changes, blog posts and documents, and connecting a domain to a site

In a Chosen sites connection the level covers sites only.

The agent asks for the permissions it wants when it connects. A level or permission it did not ask for cannot be chosen. For example, an agent that asks only for site permissions gets no access to documents even if you choose the whole team.

Creating a new site​

The agent can start an entirely new site and build it itself. This needs a Whole team connection and at least the Edit level.

  1. The agent creates the site in the team. The site gets a free trial period and the address {site}.kskamu.app
  2. Kamu.build sets up a starting point: a front page, a contact page, a privacy policy and a blog. This takes a minute or two. No AI writes content at this stage, so no agent credit is used
  3. The agent writes the content and publishes it like on any other site. Publishing needs the Edit and publish level. The published site is shown at {site}.kskamu.app

The starting point's texts are in Finnish. When the agent creates a site in another language, it rewrites the texts and sets the site's language.

The site is listed on the dashboard's Sites page like the team's other sites. No email is sent when the starting point is ready.

The trial is valid for 30 days from the last edit. A domain of its own needs a plan. The agent can start an order for a plan and a domain if the connection has the Domains and orders extra permission. You confirm and pay the order yourself, see Ordering a plan and a domain. You can also order them in the dashboard, see Plans.

The agent can create trial sites only. When the user who created the connection already has the maximum number of trial sites, no new site is created.

Extra permissions​

A Whole team connection can have extra permissions beside its level. They are chosen one at a time under Extra permissions, and none is selected by default. A Chosen sites connection cannot have them.

Extra permissionWhat it allows
ContactsMessages sent through the contact forms of the team's sites. The agent can also mark a message read
BillingThe team's invoices, agent credit and its transactions, and the sites' plans. Read only
Domains and ordersThe team's domains, searching new domains and their prices, plan prices, and starting orders for domains and plans. You always confirm and pay an order yourself

An extra permission is shown only if the agent asks for it. All permissions selects the widest level and every extra permission at once.

Contact requests contain personal data

Contact request messages contain your customers' names, email addresses, phone numbers and whatever else they wrote in the form. The agent's AI provider sees everything the agent reads. Give this permission only if it is acceptable to you and your customers that the provider processes this personal data.

Messages are cleaned before the agent gets them: invisible characters are removed, a link shows only its domain (for example [link: example.com]), and a very long field is cut. This makes it harder for instructions or links hidden in a message to steer the agent.

Ordering a plan and a domain​

With the Domains and orders extra permission the agent can search for free domains and tell you their prices and the plans' prices for your team. The price is the one the order is charged at, with VAT according to the team's billing details.

The agent can start an order with a site's plan, domains, or both. A plan can be ordered for a site on its trial, also one whose trial has already ended. A trial site cannot have its own domain, so a domain for it is ordered together with the plan in the same order.

The agent does not buy anything. It starts an order and gives you a link to the order page. There you check the order, fill in the billing and owner details, accept the terms and confirm. Only then is an invoice created and the site moved onto the ordered plan. If the team has a saved card, the invoice is charged to it after you confirm. The domain is registered only once the invoice is paid.

  • Nothing is charged, no plan is changed and no domain is reserved before you confirm. Someone else can still register the domain in the meantime
  • When one domain is ordered for a site, it is connected to the site right after registration and its DNS records are pointed at the site. The site usually shows at the address within an hour
  • An unconfirmed order expires in 7 days
  • A team can have at most 3 unconfirmed orders started by agents at a time

The agent cannot pay for anything, and it has no access to team permissions.

Connecting a domain to a site​

With the Edit and publish level the agent can connect a domain to a published site. It can be a team domain that no site uses, or a domain registered elsewhere. A trial site cannot get a domain before a plan has been ordered for it.

  • If the domain was registered or transferred through Kamu.build and its DNS is with us, the agent points the root and www records at the site. Old website records are replaced, email records stay
  • For a domain managed elsewhere the agent tells you which DNS records to add at the domain's provider. The same list is on the site's Domains page

The address usually works within an hour of the records resolving. The status is on the site's Domains page, and the agent can check it.

Who the agent acts as​

The agent acts as the user who creates the connection. If an outside agency works on the site, first invite the agency's person on the site's Users page. They create the connection with their own account and choose the site.

The role limits the level:

  • A Viewer can only give the agent the Read level. If even one of the chosen sites is one where you are a viewer, the other levels cannot be chosen
  • An Editor and team members can give any level

If the user's role changes, they are removed from the site or they leave the team, the agent's permissions change with it. A Whole team connection ends when the user is no longer a member of the team.

Editing and publishing​

Changes are made in two steps:

  1. Save. The agent makes the changes in a draft version and saves it. The public site does not change. The draft has no public address of its own, but the save returns a link that opens it in the Studio preview. Studio can be opened by members of the site's team; a user invited only to the site cannot open it yet
  2. Publish. The agent publishes the saved version. This needs the Edit and publish level

Blog posts work the same way: the agent writes a draft, which shows on the dashboard's Posts page, and publishes it separately.

Publishing takes effect at once

With the Edit and publish level the agent publishes without a separate approval. If you want to check changes before they go live, choose the Edit level, check the draft in Studio and publish it yourself. Blog posts you publish on the Posts page.

A published change can be undone on the site's History page by restoring an earlier version.

Tools​

The agent only sees the tools its level and extra permissions cover.

LevelTools
Readlist_sites, get_site_info, get_visitor_stats, get_recent_deployments, list_versions, get_file_tree, read_file, show_changes, list_blog_posts, get_site_domain
Editcreate_version, text_edit, write_file, create_file, delete_file, save_version, create_blog_post, update_blog_post, and with a Whole team connection create_site
Edit and publishpublish_version, publish_blog_post, link_domain
Extra permission Contactslist_contact_requests, get_contact_request, mark_contact_request_read
Extra permission Billingget_billing_summary, list_invoices, get_invoice
Extra permission Domains and orderslist_domains, search_domains, check_domain, list_plans, start_order, get_order

The document tools are listed on Documents over MCP.

The OAuth scopes behind the levels are site.read, site.edit, site.publish and documents.read, documents.edit, documents.publish, and for the extra permissions contacts.read, billing.read and domains.buy. A call to a tool outside the granted scopes is refused with insufficient_scope, and nothing is done.

What the agent has done​

Kamu.build records every change an agent makes through its connection: creating sites, file edits, saves, publishes, blog posts, changes to documents, marking a contact request read, connecting a domain to a site, and starting orders for domains and plans.

Of the reads, those of confidential information are recorded: reading contact requests, invoices and billing details, and the content of documents. When the agent reads the same thing several times in a row, it is recorded once per ten minutes. Reading a site's files is not recorded. The content that was read or changed is not stored in the records.

  • In your profile under Connected apps, each agent has Recent actions: the time, what the agent did and to which site or document. For an order, the ordered plan and domains are shown
  • A site's History page has a Changes by apps section once an agent has changed the site. Team owners and admins see every agent's changes on the team's sites there, including those of an agency invited to the site. Others see the changes of their own agents
  • Did not succeed means the agent attempted a change but got an error, and nothing changed

The records are kept for a year. The agent itself cannot read them.

Removing a connection​

Connected agents are listed in your profile under Connected apps. There you see whether the connection covers the whole team or chosen sites, its level and last use, and can remove the connection. After removal the agent can no longer reach your sites or documents.

Good to know​

  • Images cannot yet be added over MCP. Add them on the Media page or in Studio
  • An agent can make at most 60 tool calls per minute
  • Kamu.build does not charge for MCP use. The agent's AI usage is paid to its own provider
  • The user who created the connection is responsible for the content and for what is published