A website builder your own agent can use

Beste runs a Model Context Protocol server with more than 70 tools for pages, sections, blog posts, products, forms, redirects and publishing. Run npx beste-agent@latest in your terminal: it signs you in through the browser, connects Claude Code to your account and opens it. The agent publishes only when you ask.

  • More than 70 documented tools, each labeled read or write
  • Content is validated, and errors name the exact field
  • Changes go to the draft in batches, and most batches can be undone
Pulley and rope hanging from a wooden beam
$npx beste-agent@latest

What an agent needs from an API

An agent works from tool descriptions and error messages. This server is built so an agent can read an error, fix the request and try again.
Hand tools hanging in order on a wall rack
Tools70+ available
list_pages
update_section
create_page
undo_batch

Tools that say what they change

More than 70 tools, each labeled with what it reads and what it writes. An agent can tell a safe call from a destructive one before it makes the call.

Errors an agent can fix

A rejected request returns the field path and the expected values. The agent can correct the request and try again without a person reading the error.

Nothing goes live without you

Every change goes to the draft first, grouped in batches, and most batches can be undone. The agent publishes only when you ask, and deleting a blog post needs your confirmation.

Rope tied around a wooden post
api.beste.co/mcpAgent access
Read pages and sections
Allowed
Write to the draft
Allowed
Publish when you ask
Allowed
Delete a blog post
Needs you

One-command sign-in, validated content and batch undo

These are the same tools the Connector for Claude uses. The difference is where you work: npx beste-agent@latest connects Claude Code in your terminal, and the connector works in the Claude apps.

  • Sign in with npx beste-agent@latest and sign out to revoke access
  • Labels that show what each tool reads and writes
  • Validation errors that name the rejected field
  • Batch undo on most changes
  • Search sections and pieces by meaning
  • A health endpoint that reports what is deployed

What happens when you ask your agent for a change

Your agent looks at your site first and changes it second, so each edit lands where you meant it.
01

It finds your site

The agent sees your sites and every page on them, so it knows where things are before it touches anything.

Sites and pages

02

It reads the page

It reads the page the way you wrote it, section by section, and finds the exact sentence you asked about.

Your words, as written

03

It picks the right section

When a page needs something new, it chooses from hundreds of sections designed to work together, the same ones you pick in the editor.

From the library

04

It starts from what is there

Before it edits a section, it reads the current version, so the changes you made yourself stay in place.

Nothing overwritten

05

It saves to your draft

Every change goes to your draft. If you do not like a change, ask the agent to undo it. Visitors see nothing until you ask it to publish.

You decide when

Questions about the MCP server

Run npx beste-agent@latest and start building with your agent

Made with BesteUpgrade to Pro