Model Context Protocol (MCP) server for freee API integration
Bukku MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Bukku contacts, accounts, invoices, bills and journals; create contacts and sales invoices.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bukku-mcp-by-usefulapi https://bukku.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# bukku_list_contacts, bukku_get_contact, bukku_list_contact_groups and 20 more
Bukku MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bukku-mcp-by-usefulapi https://bukku.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List contacts (customers, suppliers, employees) with name, code, type, receivable and payable balances. Search matches the name, receivable, payable and created date. GET /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Keywords in the name, receivable, payable or created date (max 100 characters). |
| type | string | no | Only this contact type. |
| status | string | no | ACTIVE (default), INACTIVE (archived) or ALL contacts. |
| group_id | integer | no | Only contacts in this contact group (see bukku_list_contact_groups). |
| sort_by | string | no | — |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One contact with its persons, addresses, tax and registration numbers, default accounts and credit limit. GET /contacts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | Bukku contact id. |
List the contact groups; use their ids to filter bukku_list_contacts. GET /contacts/groups.
No parameter schema on file.
List ledger accounts from the chart of accounts, optionally by category. Account ids are used on invoice lines. GET /accounts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Keywords to search for in the accounts (max 100 characters). |
| category | string | no | — |
| is_archived | boolean | no | true to show deactivated accounts instead of active ones (default false). |
| sort_dir | string | no | Sort direction. |
One ledger account by id. GET /accounts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | integer | yes | Bukku account id. |
List products and bundles (sales and purchase details, SKU, stock). GET /products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Keywords in the name, SKU, sale or purchase description or remarks (max 60 characters). |
| mode | string | no | Only products sold or only products purchased. |
| type | string | no | — |
| include_archived | boolean | no | true to include archived products. |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One product with its units, prices, accounts and tax settings. GET /products/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | Bukku product id. |
List the product groups. GET /products/groups.
No parameter schema on file.
List sales invoices with number, date, contact, amount, balance and payment status. Filter by date, customer, payment status (PAID, OUTSTANDING, OVERDUE) or keywords. GET /sales/invoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | no | Invoices dated on or after this day, yyyy-mm-dd. |
| date_to | string | no | Invoices dated on or before this day, yyyy-mm-dd. |
| contact_id | integer | no | Only invoices of this customer. |
| payment_status | string | no | — |
| payment_mode | string | no | — |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | Keywords in the number, reference, title, remarks, description, contact or billing/shipping party. |
| sort_by | string | no | — |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
List quotes, sales orders, delivery orders, credit notes, customer payments or refunds (invoices have their own tool, bukku_list_sales_invoices). payment_status applies to credit notes, payments and refunds only. GET /sales/{quotes|orders|delivery_orders|credit_notes|payments|refunds}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Which sales document to list. |
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| contact_id | integer | no | Only documents of this customer. |
| payment_status | string | no | Credit notes (PAID, OUTSTANDING, OVERDUE), payments and refunds (PAID, OUTSTANDING). Not for the other types. |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | — |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One sales document in full (lines, taxes, terms, payments, status): an invoice, quote, order, delivery order, credit note, payment or refund. GET /sales/{type}/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Document type. |
| transaction_id | integer | yes | Bukku transaction id. |
List purchase bills with number, date, supplier, amount, balance and payment status. Filter by date, supplier, payment status (PAID, OUTSTANDING, OVERDUE) or keywords. GET /purchases/bills.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | no | Bills dated on or after this day, yyyy-mm-dd. |
| date_to | string | no | Bills dated on or before this day, yyyy-mm-dd. |
| contact_id | integer | no | Only bills of this supplier. |
| payment_status | string | no | — |
| payment_mode | string | no | — |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | — |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
List purchase orders, goods received notes, supplier credit notes, supplier payments or refunds (bills have their own tool, bukku_list_purchase_bills). payment_status applies to credit notes, payments and refunds only. GET /purchases/{orders|goods_received_notes|credit_notes|payments|refunds}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Which purchase document to list. |
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| contact_id | integer | no | Only documents of this supplier. |
| payment_status | string | no | Credit notes (PAID, OUTSTANDING, OVERDUE), payments and refunds (PAID, OUTSTANDING). Not for the other types. |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | — |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One purchase document in full (lines, taxes, terms, payments, status): a bill, order, goods received note, credit note, payment or refund. GET /purchases/{type}/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Document type. |
| transaction_id | integer | yes | Bukku transaction id. |
List manual journal entries by date, status or keywords. GET /journal_entries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | Keywords in the number, reference, title, remarks or description. |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One journal entry with its debit and credit lines. GET /journal_entries/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_id | integer | yes | Bukku transaction id of the journal entry. |
List banking transactions: money in (incomes), money out (expenses) or transfers between accounts. contact_id and sort_by do not apply to transfers. GET /banking/{incomes|expenses|transfers}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Which banking transactions to list. |
| date_from | string | no | A date, yyyy-mm-dd. |
| date_to | string | no | A date, yyyy-mm-dd. |
| account_id | integer | no | Only transactions on this bank/cash account (see bukku_list_accounts). |
| contact_id | integer | no | Only this contact (money in / money out). |
| status | string | no | Only transactions with this status. Without it every status except void is returned. |
| search | string | no | Keywords in the number, reference, title, remarks, description or contact. |
| sort_by | string | no | Money in / money out only. |
| sort_dir | string | no | Sort direction. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | no | Results per page, 1-100 (default 30). |
One money in, money out or transfer transaction in full. GET /banking/{incomes|expenses|transfers}/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Transaction type. |
| transaction_id | integer | yes | Bukku transaction id. |
List the tags (labels) that can be put on transactions. GET /tags.
No parameter schema on file.
Reference data needed to fill in documents: tax codes, payment terms, payment methods, currencies, countries, accounts, contact groups, product groups, price levels, tag groups, number formats, custom fields and company settings. Read-only (POST /v2/lists is a read endpoint).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lists | array | yes | Which lists to return, for example ["tax_codes", "terms"]. |
WRITE: create a contact (customer, supplier and/or employee) in Bukku. The contact code must be unique (A-Z, 0-9, _ and -, max 15 characters). POST /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| legal_name | string | yes | Legal name of the contact. |
| contact_code | string | yes | Unique code, for example C-A0001. |
| entity_type | string | yes | Entity type (used for MyInvois). |
| types | array | yes | Contact types; a contact can be several. |
| other_name | string | no | Trading or display name. |
| reg_no_type | string | no | Registration number type; send together with reg_no. |
| reg_no | string | no | Registration number. Required for MALAYSIAN_COMPANY (with reg_no_type); individuals need it or tax_id_no. |
| tax_id_no | string | no | Malaysian TIN / tax id (11-14 characters). Required for MALAYSIAN_COMPANY; individuals need it or reg_no. |
| string | no | — | |
| phone_no | string | no | — |
| remarks | string | no | — |
WRITE: archive (is_archived true) or restore (false) a contact. Archiving hides it from active lists; nothing is deleted. PATCH /contacts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | Bukku contact id. |
| is_archived | boolean | yes | true to archive, false to unarchive. |
WRITE: create a sales invoice for a customer. status defaults to draft (nothing posted to the ledger), status ready finalizes it and affects the books. payment_mode credit needs term_items, cash needs deposit_items. Companies with MyInvois submission switched on must pass myinvois_action when status is ready: NORMAL (not sent), EXTERNAL (already validated elsewhere) or VALIDATE (submits the invoic
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | Customer contact id (bukku_list_contacts type customer). |
| date | string | yes | Invoice date, yyyy-mm-dd. |
| items | array | yes | Invoice lines. |
| tax_mode | string | yes | Whether unit prices include tax. |
| currency_code | string | yes | Invoice currency, for example MYR. Use the company's home currency unless invoicing in another one. |
| exchange_rate | number | yes | Rate from the home currency to currency_code. Use 1 when currency_code is the home currency. |
| payment_mode | string | no | credit (needs term_items) or cash (needs deposit_items). |
| term_items | array | no | Payment terms, for payment_mode credit. |
| deposit_items | array | no | Payment received, for payment_mode cash. |
| number | string | no | Invoice number, blank uses the default number format. |
| number2 | string | no | Reference number. |
| title | string | no | — |
| description | string | no | — |
| remarks | string | no | — |
| status | string | no | draft (default) or ready. |
| myinvois_action | string | no | MyInvois handling, only with status ready. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bukku MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bukku_list_contacts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_contact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_contact_groups | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_accounts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_account | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_products | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_product | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_product_groups | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_sales_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_sales_documents | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_sales_document | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_purchase_bills | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_purchase_documents | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_purchase_document | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_journal_entries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_journal_entry | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_bank_transactions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_bank_transaction | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_list_tags | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_get_lookup_lists | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bukku_create_contact | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bukku_set_contact_archived | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bukku_create_sales_invoice | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.12.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Bukku MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.