Start here
Introduction
Connect Claude Code to your Awesomate account and look after your website, automations, apps and Knowledge by asking in plain words. What it is, what it can do on each plan, and how it stays safe.
The Awesomate MCP connects Claude Code to your Awesomate account. Once it is connected, you ask in plain words and Claude does the work in your account: checks why an automation failed, makes a staging copy of your website before a change, adds a page, builds an automation and tests it, answers from your Knowledge.
It runs on your own computer, inside Claude Code, and talks to your account with a key that lives only on that computer. Setting it up takes about two minutes from the hub: see the Quickstart.
What you can ask for
| Area | For example | Guide |
|---|---|---|
| Your website | "Make a staging copy and update the opening hours on the contact page." | Website |
| Automations | "Why did the invoice workflow fail last night?" | Automations |
| Apps | "Build me a booking page for my studio, and put it on bookings.mysite.com.au." | Apps |
| Knowledge | "Add our price list and returns policy to my Knowledge, then ask it about refunds." | Knowledge |
| 1Brain | "Build an agent that answers my team's questions from our procedures in 1Brain." | 1Brain |
| Contacts and portals | "Make a portal where my customers can see their own jobs." | Contacts and portals |
| Getting help | "This isn't working, can you raise a ticket for me?" | Support |
What each plan can do
| Every plan | Support Plus and above | |
|---|---|---|
| Look | How your website and automations are doing, why something failed, your plan and limits | |
| Knowledge | Answers from your Knowledge, adding sources, agents | |
| Build | Agents in your automations | Build and test automations, apps with a test copy first, staging copies and backups of your website, working on your hosting directly |
| Help | Ask Awesomate's own help, raise a support ticket | Tickets on any subject |
Apps your customers sign in to, and asking our team to build an automation for you, are Pro and above. Contacts, and with it your apps' own tables and portals, is reaching accounts in stages. If it isn't on your account yet, Claude says so, and so does the hub. When something isn't on your plan, Claude says so plainly and tells you which plan has it. It never pretends it can.
How it stays safe
- One account at a time, always named. Every answer says which account Claude is working on. See How it works.
- Nothing that deletes, replaces or spends without your yes. Deleting a WordPress site, replacing a live site with its staging copy or spending a credit is confirmed with you first, and the hub refuses what your plan or your privacy settings don't allow, whatever Claude asks for.
- No passwords or card numbers in the chat. Payments and privacy switches happen in the hub; secrets go through a one-time secure form, not the conversation.
Sister docs
The Awesomate SDK is for code you write: apps on your own data. These docs are for Claude Code working on your account. They cover the same account and the same data, so Claude can set up what the SDK then uses.
For AI tools
These docs are published as plain text too: llms.txt lists the pages and llms-full.txt has all of them in one file.