Docs

AI agents (MCP)

Let Claude or another AI agent create, configure and build your apps with an API token.

WebsiteTo.app runs a Model Context Protocol (MCP) server. Give an AI agent such as Claude an API token and it can do what you would do in the dashboard: create an app from a URL, set the logo and colours, configure permissions and integrations, request builds, check their status and hand you the download links.

1. Create an API token

Open Settings → API tokens & AI agents, name the token and pick what it may do. The token is shown once, so copy it then. Tokens can expire and can be revoked at any time, which cuts off the agent immediately.

read (always): list apps and builds, see plans and subscriptions, download builds.
write: create and edit apps, set the logo, configure OneSignal and AdMob, request free demo builds, delete apps.
spend: production builds, subscription checkout and billing portal links, cancelling queued builds.
publish: save an App Store Connect API key.

Start with read and write; add spend only when you want the agent to start production builds.

2. Connect your agent

The endpoint is https://www.websiteto.app/api/mcp and the token goes in an Authorization: Bearer header.

Claude Code

claude mcp add --transport http websiteto https://www.websiteto.app/api/mcp   --header "Authorization: Bearer wta_your_token"

Other MCP clients (Cursor, VS Code, and similar)

{
  "mcpServers": {
    "websiteto": {
      "url": "https://www.websiteto.app/api/mcp",
      "headers": { "Authorization": "Bearer wta_your_token" }
    }
  }
}

Claude API (MCP connector)

"mcp_servers": [{
  "type": "url",
  "name": "websiteto",
  "url": "https://www.websiteto.app/api/mcp",
  "authorization_token": "wta_your_token"
}]

The client has to support sending a custom header (or an authorization token). Connectors that only offer browser sign-in (OAuth) cannot use API tokens yet.

3. Ask for what you want

Create an app for https://mystore.com called "My Store" with this logo:
https://mystore.com/logo.png. Use a dark blue splash screen, turn on push
notifications, and tell me when the demo builds are ready.

Tools

Tool	Permission	What it does
`get_account`	read	Plans, prices, trial length and how long builds are kept
`list_apps, get_app`	read	Your apps, and one app's configuration, subscription and what is missing for a production build
`list_builds, get_build_download_url`	read	Build history with errors, and 60-minute download links
`create_app`	write	New app from a URL (and optional logo URL); free demo builds start automatically
`update_app, set_app_logo`	write	Name, website, colours, splash, versions, package name and bundle id, permissions, age compliance, icon
`configure_integrations`	write	OneSignal and AdMob
`request_demo_build`	write	Free Android or iOS demo
`delete_app`	write	Permanent deletion; needs the exact name and explicit confirmation, and no active subscription
`request_build, cancel_build`	spend	Production Android or iOS build (needs a subscription), and cancelling a queued one
`create_subscription_checkout, create_billing_portal_link`	spend	Stripe links for you to subscribe an app, or to change or cancel the plan; nothing is charged until you pay
`connect_app_store_connect`	publish	Save your App Store Connect API key for iOS builds

Staying in control

A token only ever acts on your own apps and subscriptions, and never as an administrator.
Tools that start production builds, create billing links or delete data refuse to run without an explicit confirm, and tell the agent to ask you first.
Private keys you give the agent are stored privately and are never returned by any tool.
Revoking a token in Settings stops it immediately. Treat tokens like passwords and never paste them into a website or a public repository.
Not available through MCP, by design: custom Android keystores. Use the dashboard for those. You still submit to the App Store and Google Play yourself.