Your connection

Remote MCP URL: https://buildasite.ai/api/mcp. Choose OAuth. Your AI client registers automatically; you do not need an API key or client secret. Sign in to your existing BuildASite account, select a workspace and optionally one site, review the requested permissions, and approve. Only workspace owners and admins can connect.

Sign in and approve

• Give your agent https://buildasite.ai/api/mcp. Its MCP client discovers the account authorization flow and opens the BuildASite login page.
• Sign in to BuildASite, choose your workspace and optionally a single website, review the permissions, and click Approve access.
• Return to your agent. It receives a scoped connection automatically; you do not paste a password, API key or token into the chat.

Create and edit on Free

Create: Use BuildASite to create a static Astro landing page for a fictional local bakery. Generate the complete files in this chat. Create a project, create its website child, read its draft, then call submit_source. Read /docs/projects and the external-source guide first. Show me the private preview and wait for my approval before publishing.

Edit: Read my BuildASite site and current draft revision. Change the hero headline to Fresh bread, every morning. Preserve the other source and resource bindings. Submit the COMPLETE updated source with submit_source and the current expectedVersion. Show the verified private preview. Do not publish yet.

Free includes one project/domain with one website, one funnel and 1,000 shared monthly visitors. Use create_project, create_project_child and submit_source; create_site/edit_site use paid platform AI and fail on Free. Poll get_run until committed, review preview_site, and publish only after approving the exact revision. The connection needs sites.read, sites.write and, for publishing, sites.publish. Managed forms and calendars can be created, configured and activated directly with create_resource and save_resource. Refresh/reconnect cached MCP tools after platform updates. Workspace management additionally needs workspace.read/workspace.write and all-sites access; new consent shows these permissions explicitly.

Manage access

Dashboard → Developer access lists connected AI apps, their workspace/site scope, permissions and expiry. Disconnect immediately disables access and refresh. Connections last at most 30 days, with hourly access tokens and rotating refresh tokens. Reconnect after expiry or to change the site boundary or permissions. Uncheck permissions you do not want to grant. A site-bound connection cannot create a second site.

A publishing permission lets the app request publication; each publish operation still requires your explicit approval for the exact saved revision. Tracking changes need tracking.write. API keys remain available for scripts and REST clients.

Troubleshooting

• Start again from your client if a connection request expires or the authorization code was already used.
• For unknown-client or redirect errors, recreate the custom connection with OAuth/DCR. Supported callbacks are the official ChatGPT and Claude URLs and local CLI /callback URLs; arbitrary callback domains are refused.
• If your workspace is absent, check that you are its owner/admin. Account creation is currently closed; use an existing approved BuildASite account.
• Reconnect if access was revoked, your membership changed, the 30-day grant expired or a refresh token was replayed. Keep credentials out of chat messages and website source.
• If a tool is absent, reconnect with the corresponding permission. A connector cannot bypass your Free plan, source/build limits or managed-resource publishing checks.