AussyPrompt ONE

ONE for developers

Connect ONE to Claude Code, Cursor, VS Code and other AI coding tools, or call it from your own code. Included with ONE Pro and ONE Agency.

Last updated: 16 November 2026

1. What it is

AussyPrompt ONE turns what a business needs into a build blueprint (roles, tables, screens, automations and KPIs) and a build pack for the tools it builds with. Developer access lets your AI coding tool use ONE directly, so it builds from the blueprint instead of guessing:

  • read your projects, blueprints and build packs (SQL, build prompts, workflows, dashboard guides);
  • ask ONE for a new blueprint or a change, then get the prompts and SQL for only what changed;
  • ask Build Doctor why something broke, and get one fix;
  • pick up this month's Grow moves and add them to the system.

It works as an MCP server (for Claude Code, Cursor, VS Code, Windsurf and other tools that support the Model Context Protocol) and as a REST API with the same tools, for your own scripts and automations.

Developer access comes with ONE Pro and ONE Agency. See pricing.

2. Connect Claude by signing in

Claude's apps (claude.ai, Claude Desktop and the Claude mobile apps) connect by signing in, with no key to copy. So does any MCP tool that supports sign-in (OAuth).

  1. In Claude, open Settings → Connectors and choose Add custom connector.
  2. Name it AussyPrompt ONE and paste https://aussyprompt.com/api/mcp as the URL.
  3. Press Connect, sign in with your ONE account and press Allow.

In Claude Code, add the server without a key, then type /mcp, choose aussyprompt and sign in:

Claude Code sign-in
claude mcp add --transport http aussyprompt https://aussyprompt.com/api/mcp

The app works as you, inside your ONE workspace, just like a key. It shows under Connected apps in ONE → Developer access, where you can disconnect it at any time. Anyone can sign in, but only ONE Pro and ONE Agency plans can approve an app.

3. Make an API key

  1. Sign in and open ONE → Developer access.
  2. Press New API key and give it a name, such as "Claude Code on my laptop".
  3. Copy the key into your tool straight away: it's shown once. We only keep a fingerprint of it.

A key works as you, inside your ONE workspace: it sees your workspace's projects and nothing else. You can have 5 keys at a time; make one per tool or computer, so you can revoke one without touching the others. Revoking a key, or a plan without developer access, stops it working straight away.

Keep keys out of code you share or commit, and never paste one into a chat or a prompt.

4. Connect your tool

ONE's MCP server is at https://aussyprompt.com/api/mcp (Streamable HTTP). For a key, put it where it says apone_YOUR_KEY.

Claude Code

Run in your terminal, in the project folder (add --scope user to use it in every project).

Claude Code
claude mcp add --transport http aussyprompt https://aussyprompt.com/api/mcp --header "Authorization: Bearer apone_YOUR_KEY"

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project).

Cursor
{
  "mcpServers": {
    "aussyprompt": {
      "url": "https://aussyprompt.com/api/mcp",
      "headers": {
        "Authorization": "Bearer apone_YOUR_KEY"
      }
    }
  }
}

VS Code (Copilot)

Add to .vscode/mcp.json. VS Code asks for the key once and keeps it safe.

VS Code (Copilot)
{
  "inputs": [
    {
      "type": "promptString",
      "id": "aussyprompt-key",
      "description": "AussyPrompt ONE API key",
      "password": true
    }
  ],
  "servers": {
    "aussyprompt": {
      "type": "http",
      "url": "https://aussyprompt.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:aussyprompt-key}"
      }
    }
  }
}

Windsurf and others

Any MCP client that supports remote (Streamable HTTP) servers: add the URL and the Authorization header.

Windsurf and others
{
  "mcpServers": {
    "aussyprompt": {
      "serverUrl": "https://aussyprompt.com/api/mcp",
      "headers": {
        "Authorization": "Bearer apone_YOUR_KEY"
      }
    }
  }
}

Then just ask, for example:

  • “Use AussyPrompt ONE: list my projects, open the salon booking app and build it from its blueprint.”
  • “Get the Supabase SQL from my ONE build pack and set up the database.”
  • “The login page fails with a 401. Ask Build Doctor what's wrong and apply its fix.”
  • “Ask ONE to add a discount field to Invoices, then apply only what changed.”

5. Limits and costs

  • Three tools call the AI: create_project, change_blueprint and ask_build_doctor. They take up to a few minutes and use the same monthly allowance as in ONE (new blueprints, blueprint changes and Build Doctor diagnoses). get_usage shows what's left. Allowances reset on the 1st.
  • Every other tool is free to use and answers straight away.
  • Each key can make up to 120 requests a minute. The AI tools also have hourly limits, shared with your use of ONE.
  • Screenshots sent to Build Doctor go to the AI and are not stored.

6. Tools

The same 15 tools are served over MCP and REST. Tools marked AI use your monthly allowance.

get_usage

GET /api/v1/usage

Your ONE plan and what's left this month: projects, new blueprints, blueprint changes and Build Doctor diagnoses. Limits reset on the 1st.

list_projects

GET /api/v1/projects

Every ONE project in your workspace, newest first: id, title, type, status, build tools and blueprint size.

get_project

GET /api/v1/projects/{project_id}

One project with its full blueprint (roles, tables and fields, screens, automations, KPIs, rules, assumptions and open questions), the brief it came from and the launch checklist. format=markdown returns the blueprint as a readable spec instead of JSON.

  • project_id stringrequired: The project's id, from list_projects.
  • format json | markdown: json (default) or markdown.

create_projectAI

POST /api/v1/projects

Starts a new ONE project: ONE turns your brief into a full build blueprint, checks its own work and fixes what it finds. Takes 1 to 3 minutes and uses one of the month's new blueprints. The brief can be in any South African language. Show the returned open questions to the business owner. If the connection drops, the run carries on: call list_projects after a few minutes.

  • title stringrequired: The project's name.
  • kind automation | app | dashboard | system | websiterequired: automation, app, dashboard, system or website.
  • brief stringrequired: What the business needs, in as much detail as you have (at least 60 characters).
  • targets array of 12 choicesrequired: The tools it will be built with: lovable (Lovable / Bolt / v0), supabase (Supabase), mysql (MySQL (Hostinger / cPanel)), cursor (Cursor / Claude Code), n8n (n8n), make (Make), zapier (Zapier), powerautomate (Power Automate), sheets (Google Sheets / Excel), looker (Looker Studio), powerbi (Power BI), agent (AI Agent).

change_blueprintAI

POST /api/v1/projects/{project_id}/change

ONE applies a change to a project's blueprint, in plain words (e.g. "Add a discount field to Invoices and show it on the invoice screen"), and checks its work. Takes 1 to 3 minutes and uses one of the month's blueprint changes. The earlier blueprint is kept as a version. Afterwards, get_changes gives the prompts and SQL for only what changed.

  • project_id stringrequired: The project's id, from list_projects.
  • change stringrequired: The change, in plain words.

update_blueprint

PUT /api/v1/projects/{project_id}/blueprint

Replaces a project's blueprint with one you edited yourself (the same JSON shape get_project returns). No AI call, so it doesn't use an allowance. ONE tidies it to the blueprint rules and keeps the earlier one as a version. Returns what changed.

  • project_id stringrequired: The project's id, from list_projects.
  • blueprint objectrequired: The complete blueprint object.

get_build_pack

GET /api/v1/projects/{project_id}/pack

The build pack ONE makes from the blueprint: database SQL, build prompts, automation workflows, dashboard guides and the launch checklist, for each of the project's build tools. Lists the files; read each with get_build_file. target narrows it to one tool.

  • project_id stringrequired: The project's id, from list_projects.
  • target lovable | supabase | mysql | cursor | n8n | make | zapier | powerautomate | sheets | looker | powerbi | agent: Only this build tool's files (plus the general ones).

get_build_file

GET /api/v1/projects/{project_id}/pack/file

One file from the build pack, by its path from get_build_pack (e.g. a Lovable build prompt, the Supabase SQL or an n8n workflow).

  • project_id stringrequired: The project's id, from list_projects.
  • path stringrequired: The file's path, from get_build_pack.

check_project

GET /api/v1/projects/{project_id}/check

ONE's automatic checks on the blueprint and build pack: problems that would break the build (fails) and things worth a look (warns). No AI call.

  • project_id stringrequired: The project's id, from list_projects.

get_changes

GET /api/v1/projects/{project_id}/changes

After a blueprint changes, the prompts and SQL that take a system already built to the new blueprint, without rebuilding it. Compared with the version you marked as built (since=built, the default) or with the blueprint before the last change (since=previous). Lists the files and returns CHANGES.md; pass path for another file. Call mark_built once the changes are applied.

  • project_id stringrequired: The project's id, from list_projects.
  • since built | previous: built (default) or previous.
  • path string: A file from the list, to read it.

mark_built

POST /api/v1/projects/{project_id}/built

Tells ONE the current blueprint is what's now built, so the next get_changes only covers newer changes. Also moves a new project to Building.

  • project_id stringrequired: The project's id, from list_projects.

ask_build_doctorAI

POST /api/v1/projects/{project_id}/doctor

Something broke while building? Build Doctor reads the blueprint, the build pack for that tool and earlier problems, works out the cause (build, setup, plan or working as planned) and gives one fix: a small prompt, steps by hand, or a blueprint change. Pass follow_up_of with an earlier diagnosis id when its fix didn't work (2 follow-ups are free). Uses one of the month's diagnoses. Never include passwords, API keys or tokens.

  • project_id stringrequired: The project's id, from list_projects.
  • tool stringrequired: The tool it broke in: lovable, supabase, mysql, cursor, n8n, make, zapier, powerautomate, sheets, looker, powerbi, agent or other.
  • problem stringrequired: What went wrong, with the exact error message.
  • step string: The launch checklist step they were on, if any.
  • follow_up_of string: An earlier diagnosis id, when its fix didn't work.
  • images array: Up to 3 screenshots, base64 (PNG, JPEG, WebP or GIF, 4 MB each). They aren't stored.

list_diagnoses

GET /api/v1/projects/{project_id}/diagnoses

A project's Build Doctor diagnoses, newest first, with the fix each one gave and whether it worked.

  • project_id stringrequired: The project's id, from list_projects.

get_grow_plan

GET /api/v1/projects/{project_id}/grow

Grow your business: this month's three suggested moves for the business, picked from its own blueprint and its monthly numbers, plus the other moves that fit. Build moves can be added to the system with add_grow_move; today moves come with ready-to-use messages.

  • project_id stringrequired: The project's id, from list_projects.

add_grow_move

POST /api/v1/projects/{project_id}/grow/moves

Adds a Grow build move to the project's blueprint (e.g. review requests or a loyalty card). No AI call. The earlier blueprint is kept; then get_changes gives the prompts for only this move.

  • project_id stringrequired: The project's id, from list_projects.
  • move_id whatsapp-status | google-profile | click-to-chat | win-back | reviews | referral | enquiries | weekly-report | staff-bonus | cash-up | reminders | low-stockrequired: The move's id, from get_grow_plan.

7. REST API

The base URL is https://aussyprompt.com/api/v1. Send your key with every request as Authorization: Bearer apone_…. Bodies and answers are JSON; errors come back as {"error": "…"} with a matching status (400, 401, 403, 404, 409 or 429).

List your projects
curl https://aussyprompt.com/api/v1/projects -H "Authorization: Bearer apone_YOUR_KEY"
  • Path parts such as {project_id} come from the URL; other GET inputs are query parameters, and POST and PUT inputs go in the JSON body.
  • The AI tools answer 202 straight away with a job_id. Follow it with GET /api/v1/jobs/{job_id} every few seconds until status is done (with the result) or failed (with the error). Jobs are kept for an hour.
  • GET /api/v1/projects/{project_id}/pack.zip downloads the whole build pack.