BizHub365 connector for AI assistants
Lets an AI assistant work in BizHub365 for you, as the owner of a business or as the accountant of a client. It works with Claude and other MCP clients. Not made or endorsed by Anthropic.
In plain words
- It signs in as you, through the BizHub365 website, for one business that you choose. Your password is never typed into it or shown to the assistant.
- What the assistant reads (customers, invoices, bank lines) is sent to the AI provider you use, under your own agreement with them. BizHub365 does not send your data to that provider and does not control the assistant or what the provider does with the data. If you use it for a client's business, that client's data goes to your AI provider: check that your agreement with your client allows this.
- It can never send anything to HMRC or Companies House. Risky actions (deleting, changing users or billing, anything that emails someone) need your approval, each time, on a page inside BizHub365.
- You can disconnect it at any time under Security > Connected apps in BizHub365.
- It is software, not tax or accounting advice. Check what it prepares.
More: the user guide section, Terms, Schedule A4B and Privacy Policy, connected AI assistants. Support: support@bizhub365.co.uk.
It is a client of the BizHub365 REST API, so it can do what your sign-in can do in that business, no more, and every rule BizHub365 applies (permissions, subscription, rate limits) still applies. It talks only to BizHub365 and sends no analytics or usage data anywhere.
What it covers
Features that BizHub365 offers through its REST API: finance (invoices, quotes, credit notes, expenses, suppliers, payments, money in, daily takings, bank feeds and reconciliation, ledger accounts), reports, payroll, preparing tax figures, Companies House look-ups, customers, bookings, jobs, mileage, document capture, products, users and permissions, subscription, settings and audit logs. The tool list is built from BizHub365's published API description, so it follows the API. Features that exist only on the website are out of reach until they are added to the API.
What it will not do
These are refused by the server, whatever the assistant is told:
| Refused | Why |
|---|---|
| Sending anything to HMRC (VAT returns, Income Tax updates and declarations, Corporation Tax, payroll FPS and EPS, loss claims, tax calculations) | It is a declaration a person makes, with a confirmation code emailed to them. The assistant can prepare, check and explain everything up to that point, then you send it in BizHub365. |
| Sign-in, passkeys, authenticator apps, devices, changing a password, deleting an account | Yours to do. |
| Accepting legal terms, consent (Scan with AI, sharing bank data, referral programme) | A decision for the person. |
Passwords, secrets, declaration_agreed, confirmation codes in a request |
Refused wherever they appear. |
| Public and server-to-server addresses | Not for assistants. |
BizHub365 itself asks for your approval of these on its own page (above). The connector also makes the assistant ask you
first: these need confirm=true, which the assistant must only set after you have said yes to that exact action: every delete,
cancelling or changing the subscription, adding or changing users, and anything that emails someone: saving an invoice,
recording a payment, converting a quote, creating or changing a booking, invoicing time, resending, receipts, invitations, locking a VAT return or pay period, rejecting, cancelling, disconnecting.
Other protections: results have anything that looks like a secret removed; files are only uploaded from folders you name;
signed download links are followed only on the API's own address and without your sign-in; the sign-in is only ever sent
over https (http is allowed for localhost only); redirects are never followed.
Install
Needs Python 3.11 or newer.
pipx install bizhub365-mcp
(or uv tool install bizhub365-mcp, or pip install bizhub365-mcp inside a virtual environment).
Connect a business
bizhub365-mcp login
Your browser opens on the BizHub365 website. You sign in there (password and second step, as always), read what the
assistant will be able to do, choose the business, and click Allow. Your password never goes through this program or
the assistant. The program only receives a one-time code on a loopback address (127.0.0.1) and exchanges it (OAuth with
PKCE). What it keeps, in ~/.config/bizhub365-mcp/credentials.json (owner-only; on Windows this relies on your user folder's permissions, so do not use the connector on a Windows account other people sign in to), is a token for that one business; it
refreshes itself. The connection ends after 30 days unused or 90 days after you signed in, when you disconnect it, when you
change your password or your sign-in email, if your account is switched off, if you leave the business, or if the business
is deleted; then you run login again.
One connection is for one business. An accountant connects each client once, with a name for it:
bizhub365-mcp login --profile acme
bizhub365-mcp profiles # the businesses you have connected
bizhub365-mcp logout --profile acme
bizhub_list_businesses and bizhub_select_business in the assistant switch between the businesses you have connected.
A connection never reaches another business, whatever the assistant asks. You can also disconnect an app any time in
BizHub365 under Security > Connected apps. Staff accounts cannot connect.
Risky actions (deleting, users, billing, anything that emails someone) need your go-ahead, on a page inside BizHub365: the assistant shows you a link, you check what it will do and approve, then it repeats the request. The assistant cannot approve for you, and sending to HMRC or Companies House is never possible from here.
An account that is limited because updated terms are not yet accepted must accept them on the website first.
Add it to your client
Claude Code:
claude mcp add bizhub365 -- bizhub365-mcp
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"bizhub365": { "command": "bizhub365-mcp" }
}
}
Add "env": { ... } to either for the settings below.
Using it
Start by asking it to check the connection, then work in plain words:
- "List my businesses and select Acme Plumbing."
- "Which invoices are overdue? Draft a polite reminder for each customer." (It asks before emailing anyone.)
- "Review October's books and tell me what needs fixing."
- "Prepare the VAT return for this quarter and explain each box." (You send it to HMRC yourself.)
- "I'm the accountant: check every client and rank them by what needs attention."
Built-in guided prompts: month_end_review, vat_return_prep, chase_overdue_invoices, bank_reconciliation,
year_end_checklist, client_health_check.
Tools
By default there are 10 compact tools, which keeps the assistant's context small and still reaches every operation:
bizhub_status, bizhub_list_businesses, bizhub_select_business, bizhub_list_areas, bizhub_search_operations,
bizhub_describe_operation, bizhub_read (look things up; changes nothing), bizhub_call (create, change, delete),
bizhub_business_snapshot (one-call overview of a business), bizhub_refresh_schema.
For one typed tool per operation, set BIZHUB365_MCP_TOOLSET=full, or pick areas such as
finance,hmrc_vat,payroll to get tools for just those. bizhub365-mcp tools --toolset finance lists what a setting gives.
Reads are marked read-only, so a client can allow them without asking; writes are marked so it asks.
Settings (environment variables)
| Variable | Default | Meaning |
|---|---|---|
BIZHUB365_API_URL |
https://apiv1.bizhub365.co.uk |
The API. https only (http for localhost, for development). |
BIZHUB365_MCP_TOOLSET |
compact |
compact, full, or a list of areas. |
BIZHUB365_MCP_READ_ONLY |
off | 1 refuses every change; only looking is possible. |
BIZHUB365_MCP_FILE_ROOTS |
none | Folders files may be uploaded from (receipts, attachments), separated by : (; on Windows). Uploads can be emailed on to customers, so name a dedicated folder, not your home folder. |
BIZHUB365_MCP_DOWNLOAD_DIR |
~/Downloads/bizhub365-mcp |
Where PDFs and exports are saved. |
BIZHUB365_MCP_MAX_RESPONSE_CHARS |
60000 |
Longer results are cut to fit, and say so. |
BIZHUB365_MCP_TIMEOUT_SECONDS |
30 |
Per request. |
BIZHUB365_MCP_CONFIG_DIR, BIZHUB365_MCP_CACHE_DIR |
XDG defaults | Sign-in file; cached API description (a day). |
BIZHUB365_MCP_PROFILE |
default |
Which connection to use (one per business, made with login --profile). |
BIZHUB365_SITE_URL |
derived from the API address | The BizHub365 website the browser sign-in opens (set it only for a local server). |
BIZHUB365_ACCESS_TOKEN |
none | For testing only: a token from bizhub365-mcp login. It cannot refresh. Never copy a token into shared files. Prefer login. |
Good to know
- Records are untrusted text. A customer name or a scanned document can contain instructions aimed at an assistant. The rules above hold regardless, and the assistant is told to ignore such text, but read what it proposes before approving.
- Money is in pounds as strings with two decimals; dates are
YYYY-MM-DD. - If BizHub365 is updated, run
bizhub_refresh_schema(or wait a day) to pick up new operations. - If an assistant answers that the connection has ended or expired, run
bizhub365-mcp loginagain.
Licence
See the LICENSE file. Copyright Tweed Tyne Technologies Ltd (company SC874131). "BizHub365" is a name of Tweed Tyne Technologies Ltd. The licence covers the code only. It gives no right to use the BizHub365 name or logo, and a changed copy must not be presented as BizHub365's.
Metadata
Release files for bizhub365-mcp 0.1.2
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 |
|---|---|---|---|---|
| bizhub365_mcp-0.1.2.tar.gz | 89.0 kB | Without provenance | Details for bizhub365_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bizhub365_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for bizhub365_mcp-0.1.2-py3-none-any.whl |
Total release size: 177.1 kB
Release files / bizhub365_mcp-0.1.2.tar.gz
| Download URL | bizhub365_mcp-0.1.2.tar.gz |
|---|---|
| Size | 89.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e444c154c0537bc0d14a1a3cf5ef947e301a4db5b9553ae31a1d4987d5d887e
|
|
BLAKE2b-256 checksum How to use checksums |
5e35cdd2ba61f2a00f87e564c294d5ab7e26941d0a45edbe04655a7a482105b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / bizhub365_mcp-0.1.2-py3-none-any.whl
| Download URL | bizhub365_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 88.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13c00be6a7ca128cc5808dd32af5142e521bd811fe4b396d77e83f16b5275291
|
|
BLAKE2b-256 checksum How to use checksums |
f4c5de8340c57e019c3c367bd0026eea8addce3a4995dc27ca705000759d87bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for bizhub365-mcp 0.1.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.