businessapi-mcp
MCP server for Business API — the Australian ASIC / ATO / ABRS / PPSR digital-service-provider API. Give Claude Code, Claude Desktop, Cursor or any MCP client the ability to look up ABNs and ACNs, check names, register companies, ABNs and business names, lodge ASIC agent forms, run PPSR searches, and monitor entities — with the sandbox as the default environment and every lodgement dry-run first.
You: Register a company called ACME TRADING SANDBOX TEST PTY LTD in the sandbox
Claude: check_company_name_availability → Available
get_request_schema("company_registration") → asks you for officeholders, addresses, shares
lodge_company_registration(dry_run=true) → shows you the exact payload and fees
lodge_company_registration(dry_run=false) → requestId 37363
wait_for_request → finished · ACN 601510089 · document 0EACL6550
Install in three steps
Requires uv (it fetches and runs the package; nothing else to install).
-
Get a key. Register at https://businessapi.com.au/register and create a key at https://businessapi.com.au/user/api-keys. Sandbox keys start with
bapi_sk_test_, are free and need no card. -
Store it (prompted, hidden; saved to your user config directory, verified against the API):
uvx businessapi-mcp setup
-
Register the server with your client:
uvx businessapi-mcp install claude-code # or: claude-desktop · cursor · vscode · mcp-json
This is equivalent to
claude mcp add bapi -- uvx businessapi-mcp; the key never appears in client configuration. Not on PyPI yet, or want the latest commit? Add--gitto run straight from GitHub (uvx --from git+https://github.com/JoeFu/businessapi-mcp businessapi-mcp).
Then open a new session and ask: "Which company has ABN 51 824 753 556?" (it calls lookup_abn) or
"Register a company in the sandbox". uvx businessapi-mcp doctor runs a self-test against the sandbox if anything
looks off, and uvx businessapi-mcp status shows which key and environment are active.
Manual client configuration
{ "mcpServers": { "bapi": { "command": "uvx", "args": ["businessapi-mcp"] } } }
Claude Desktop: claude_desktop_config.json. Cursor: ~/.cursor/mcp.json. VS Code: .vscode/mcp.json with
"servers": { "bapi": { "type": "stdio", "command": "uvx", "args": ["businessapi-mcp"] } }. The key is read from
the user config file written by setup, from ./.env, or from BAPI_API_KEY.
How the model knows what to do
The vendor publishes no OpenAPI specification, only HTML documentation. This project turns that documentation into three things the model receives over MCP:
- Server instructions — environment, asynchronous lodgement flow, pricing, dry-run workflow, where to start.
- Tools — 46 of them, each with a description that says when to use it, what it costs and what to call next. Lodgement bodies are validated by Pydantic models whose field names match the vendor docs one-to-one, with the ASIC/ATO code tables as enums and the "Mandatory IF …" cross-field rules as validators.
- Resources — 12 guides under
bapi://docs/*(endpoint catalogue, lifecycle, per-form guides, code tables) and the request schema of every lodgement underbapi://schemas/{form}.
Tools
| Group | Tools | Notes |
|---|---|---|
lookup |
lookup_abn lookup_acn check_company_name_availability check_business_name_availability search_business_industries |
free lookups |
registrations |
lodge_company_registration lodge_abn_registration lodge_business_name_registration lodge_business_name_renewal + status / payment-link tools, get_abn_entitlement_questionnaire, get_request_schema |
Form 201, ABNREG, BNREG, BNRENEW |
agent_forms |
lodge_asic_484_form lodge_company_name_change lodge_company_deregistration lodge_asic_361_form lodge_asic_362_form request_asic_account_transactions + status tools |
registered-agent forms 484 / 205A / 6010 / 361 / 362 / RA52 |
monitoring |
start_entity_monitoring renew_entity_monitoring list_monitored_entities get_monitored_entity stop_entity_monitoring resume_entity_monitoring get_entity_snapshot list_monitoring_events get_monitoring_event simulate_monitoring_event |
$18 per entity per year live |
webhooks |
list_webhooks create_webhook update_webhook delete_webhook rotate_webhook_secret verify_webhook_signature |
signature check runs locally |
ppsr |
create_ppsr_search get_ppsr_search |
$6 per search live |
core |
get_request_status wait_for_request get_account_status call_endpoint |
polling, account, escape hatch |
Every lodgement tool defaults to dry_run=true: it validates locally and returns the exact JSON that would be sent.
The model has to pass dry_run=false to lodge — the natural "show the user the payload and fees, then confirm" step.
Safety model
- Sandbox by default. The environment is inferred from the key prefix.
bapi_sk_test_…only ever reacheshttps://businessapi.com.au/api/test/v2, where nothing is billed and nothing reaches production registries. - Live writes are blocked unless the server runs with
BAPI_ALLOW_LIVE=true. With a live key every POST / PATCH / DELETE is refused before any HTTP call. Turn it on only when you intend to lodge. testTransmissionIndicatoris injected from the server environment and anything the model sends is ignored;simulate_monitoring_eventrefuses to run against live; monitoring orders and renewals need a caller-supplied idempotency key so retries never charge twice; TFNs are checksum-validated and never echoed; webhook secrets are returned once.- Tools carry MCP
annotations(readOnlyHint,destructiveHint) and a toolset tag.
See SECURITY.md.
Configuration
| Variable | Default | Effect |
|---|---|---|
BAPI_API_KEY |
— | the key; also read from ./.env or the file written by businessapi-mcp setup |
BAPI_ENV |
inferred from the key | test / live; only a cross-check, a mismatch is reported |
BAPI_ALLOW_LIVE |
off | must be true before any live POST / PATCH / DELETE |
BAPI_INLINE_SCHEMAS |
off | true puts the full lodgement schemas into tools/list |
BAPI_TOOLSETS |
all |
comma-separated groups to expose (see below) |
Lookup order: environment variables → ./.env in the directory the server starts from → the user config file
(%APPDATA%\businessapi-mcp\.env, ~/Library/Application Support/businessapi-mcp/.env, ~/.config/businessapi-mcp/.env).
Context size: lazy schemas and toolsets
Inlining the full schemas of the lodgement tools into tools/list costs about 147k characters (~37k tokens) on every
connection. By default the request parameter of each lodge_* tool is a plain JSON object and the model fetches the
exact schema on demand with get_request_schema(form) or bapi://schemas/{form}; validation is unchanged and errors
come back as a list of field paths.
| Configuration | Tools | Chars | ≈Tokens |
|---|---|---|---|
BAPI_INLINE_SCHEMAS=true, all toolsets |
46 | 146,619 | 36,654 |
| default (lazy), all toolsets | 46 | 52,432 | 13,108 |
BAPI_TOOLSETS=lookup,registrations,core |
18 | 20,409 | 5,102 |
BAPI_TOOLSETS=agent_forms,core |
15 | 17,893 | 4,473 |
BAPI_TOOLSETS=monitoring,webhooks |
16 | 17,012 | 4,253 |
BAPI_TOOLSETS=lookup,ppsr |
7 | 7,494 | 1,873 |
BAPI_TOOLSETS lets one package run as several small servers — see .mcp.json.example. Leaving core off a server
also removes the call_endpoint escape hatch. Re-measure with uv run scripts/tools_list_size.py.
Command line
businessapi-mcp run the MCP server on stdio (what clients launch)
businessapi-mcp run --transport http --port 8000
businessapi-mcp setup [--local] store the key (hidden prompt) and verify it
businessapi-mcp status where the key comes from, which environment is active
businessapi-mcp doctor [--lodge] sandbox self-test through the real tools; --lodge also lodges the examples
businessapi-mcp install <client> claude-code | claude-desktop | cursor | vscode | mcp-json (--dry-run, --dev REPO)
doctor refuses live keys. Its read-only run covers account status, lookups, name checks, industry search, the ABN
entitlement questionnaire, a PPSR search polled to completion, a $0 monitoring order with a simulated event and
list_webhooks; --lodge additionally submits the example company, sole-trader ABN and business-name payloads to the
sandbox and polls them (observed: company finished with a test ACN, ABN validation ok, business name
wating ASIC CC payment with an ASIC UAT payment link).
What the vendor docs get wrong (verified in the sandbox)
- Two helpers need query parameters the docs omit:
/helpers/business-industries?searchTerm=and/helpers/entitlement-questionnaire?entityType=&entitySubType=. - Every
officeHolders[]entry in a company registration needsaddressOverriddenIndicator(400 without it); the model defaults it tofalse. - Company registration POST answers
{requestId, status, billing}at the top level, not{response: {requestId}}; the finished status usesregistrationDate, notdateOfRegistration; ASIC rejections arrive aserrors[].details.text(the full advice letter) with a snake_caseresponse. - ABN lookups return PascalCase keys (
EntityName,AbnStatus, …). - Share money fields: the rules say integers in cents, the vendor sample sends
100for 100 × $1 shares, and the sandbox accepts either — agree the convention with the vendor before a live lodgement. - Several vendor samples carry the placeholder ACN
123456789, which fails the checksum their own docs require. - Endpoints without a public docs page (name reservations, extracts,
tax/registrations, most RA forms, ASIC inbox) are reachable only throughcall_endpoint.
Development
git clone https://github.com/JoeFu/businessapi-mcp && cd businessapi-mcp
uv sync --group dev
uv run pytest # offline: vendor samples, rules, server modes, CLI
uv run businessapi-mcp install claude-code --dev . # point your client at this checkout
uv run businessapi-mcp doctor # needs a sandbox key in ./.env or via setup
uv run --group dev scripts/export_openapi.py # refresh openapi.yaml after editing models.py
Layout: src/businessapi_mcp/ (server.py tools and docs, models.py request models, config.py key discovery,
cli.py, smoke.py doctor, examples/), tests/ with the vendor samples as fixtures, scripts/ (OpenAPI export,
an OpenAPI-generated alternative server, tools/list size measurement), openapi.yaml.
Adding a lodgement: write the request model in models.py, a _lodge_x(request, dry_run) implementation in
server.py, and one row in the LODGEMENTS registry; lazy / inline mode, toolset filtering and get_request_schema
follow automatically. Other tools use @tool("<group>", annotations=...).
Releases: push a v* tag; publish.yml builds and publishes to PyPI through trusted publishing.
License
MIT — see LICENSE. Not affiliated with Business API Pty Ltd, ASIC or the ATO.
Metadata
Release files for businessapi-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| businessapi_mcp-0.1.0.tar.gz | 104.0 kB | With provenance | Details for businessapi_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| businessapi_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for businessapi_mcp-0.1.0-py3-none-any.whl |
Total release size: 178.8 kB
Release files / businessapi_mcp-0.1.0.tar.gz
| Download URL | businessapi_mcp-0.1.0.tar.gz |
|---|---|
| Size | 104.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a41ad473ee9fa8f2001eeb82525b707587528820e82e9165cb0edd81147a7955
|
|
BLAKE2b-256 checksum How to use checksums |
89da4e322f8d4aa4a3b696937014735eb11c966d850b6b4ef72d4751c8a46410
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / businessapi_mcp-0.1.0-py3-none-any.whl
| Download URL | businessapi_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 74.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ef7d48d5c0d2b1a3a591af91184c3be75a0a121ce577b8848753dbe1d6e213c
|
|
BLAKE2b-256 checksum How to use checksums |
06f32f2ed425adcba95f0e3388c185b1396945b4379a16fb3bb4a60330d22a27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for businessapi-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for businessapi_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.