Model Context Protocol (MCP) server for freee API integration
Briox 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 invoices, journals and accounts; create customers, items and unposted invoices in Briox.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http briox-mcp-by-usefulapi https://briox.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# briox_get_company_info, briox_list_customers, briox_list_suppliers and 22 more
Briox 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 briox-mcp-by-usefulapi https://briox.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.
25 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.
The Briox company the connection belongs to: name, address, bank details, organization number and more. Good first call. GET /company/info.
No parameter schema on file.
List customers (custno, name, address, e-mail, phone, company number, active flag). Paged: pass next_page as page. GET /customer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_number | string | no | Only the customer with this company (organization) number. |
| modified_since | string | no | Only objects modified after this moment: yyyy-mm-dd or 'yyyy-mm-dd HH:MM'. |
| order_by | string | no | Sort column. |
| order_direction | string | no | Sort direction. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List suppliers (supplierno, name, address, e-mail, company number). Paged: pass next_page as page. GET /supplier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_number | string | no | Only the supplier with this company (organization) number. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List customer (sales) invoices with total, saldo (open amount), invoice and due date, customer. Filter by date range, status (for example overdue, unsettled, finalpayed) and type. Paged: pass next_page as page. GET /customerinvoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | no | Invoices dated on or after this day (yyyy-mm-dd). |
| to_date | string | no | Invoices dated on or before this day (yyyy-mm-dd). |
| modified_since | string | no | Only objects modified after this moment: yyyy-mm-dd or 'yyyy-mm-dd HH:MM'. |
| status | string | no | Status filter (default all): unsettled = not fully paid, overdue = past due date, finalpayed = fully paid. |
| type | string | no | Invoice type (Briox default: invoice). |
| order_by | string | no | Sort column. |
| order_direction | string | no | Sort direction. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List supplier (purchase) invoices with total, saldo, payment status, invoice and payment date, supplier. Filter by date range. Paged: pass next_page as page. GET /supplierinvoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | no | Invoices dated on or after this day (yyyy-mm-dd). |
| to_date | string | no | Invoices dated on or before this day (yyyy-mm-dd). |
| modified_since | string | no | Only objects modified after this moment: yyyy-mm-dd or 'yyyy-mm-dd HH:MM'. |
| order_by | string | no | Sort column. |
| order_direction | string | no | Sort direction. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List items (products and services) with description, unit, type, prices, VAT rate and stock. Paged: pass next_page as page. GET /item.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_item_number | string | no | Only items with this supplier item number. |
| manufacturer_item_number | string | no | Only items with this manufacturer item number. |
| modified_since | string | no | Only objects modified after this moment: yyyy-mm-dd or 'yyyy-mm-dd HH:MM'. |
| order_by | string | no | Sort column. |
| order_direction | string | no | Sort direction. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
One customer with addresses, payment terms, VAT number, delivery methods and defaults. GET /customer/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The customer id (the customer number, custno, from briox_list_customers). |
One supplier with addresses, bank details, payment terms and defaults. GET /supplier/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_id | string | yes | The supplier id (supplierno from briox_list_suppliers). |
One customer invoice with rows, totals, saldo, payment and reminder state. GET /customerinvoice/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | string | yes | The customer invoice id (id from briox_list_customer_invoices). |
One supplier invoice with rows, totals, payment status, linked files and deviations. GET /supplierinvoice/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | string | yes | The supplier invoice id (id from briox_list_supplier_invoices). |
One item (article) with prices, VAT rate, accounts, stock and supplier data. GET /item/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | string | yes | The item number (item_id from briox_list_items). |
List ledger accounts with description, VAT code, active flag and incoming balance for a financial year. Paged: pass next_page as page. GET /account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | no | The financial year id from briox_list_financial_years. |
| active | boolean | no | true = only active accounts, false = only inactive. |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List the financial years (id, from and to date, accounting method). The id is the financial year argument of the journal tools. GET /financialyear.
No parameter schema on file.
List the journal series of a financial year (for example A, B). GET /journal/series/{financialyear}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| financial_year | string | yes | The financial year id from briox_list_financial_years. |
List journal entries (vouchers with their debit/credit rows) of a financial year, optionally of one series and a date range. Paged: pass next_page as page. GET /journal/{financialyear}[/{series}].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| financial_year | string | yes | The financial year id from briox_list_financial_years. |
| series | string | no | Only this journal series (briox_list_journal_series). |
| from_date | string | no | Entries on or after this day (yyyy-mm-dd). |
| to_date | string | no | Entries on or before this day (yyyy-mm-dd). |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
One journal entry with all its debit/credit rows. GET /journal/{financialyear}/{series}/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| financial_year | string | yes | The financial year id from briox_list_financial_years. |
| series | string | yes | The journal series (for example A). |
| journal_id | string | yes | The journal id (id from briox_list_journals). |
The balances of the company's bank accounts. GET /bank/accountbalance.
No parameter schema on file.
List VAT codes with description and percentage. GET /vatcode.
No parameter schema on file.
List payment terms (the ids usable on customers and invoices). GET /payment/term.
No parameter schema on file.
List projects with leader, status, dates and customers. Paged: pass next_page as page. GET /project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List cost centers (code, text, active). Paged: pass next_page as page. GET /costcenter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
List sales orders, optionally by date range and status. Paged: pass next_page as page. GET /salesorder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | no | Orders dated on or after this day (yyyy-mm-dd). |
| to_date | string | no | Orders dated on or before this day (yyyy-mm-dd). |
| status | string | no | Status filter (default all). |
| page | integer | no | Page number (the first page is 1). Use next_page from the previous reply. |
| limit | integer | no | Results per page. |
Create a customer in Briox (the customer number custno is assigned by you; use a free number). Creates a new record; it never changes an existing one. POST /customer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| custno | string | yes | Customer number (must be unused). |
| name | string | yes | Customer name. |
| is_company | boolean | no | true = company, false = private person. |
| string | no | — | |
| phone | string | no | — |
| company_number | string | no | Company (organization) number. |
| vat_number | string | no | VAT number starting with the 2-letter country code. |
| currency | string | no | — |
| payment_terms | string | no | Payment term id from briox_list_payment_terms. |
| description | string | no | Free text note. |
| address | string | no | Invoice address, street line. |
| zip | string | no | — |
| city | string | no | — |
| country_code | string | no | — |
Create an item (a product or service) in Briox. Prices are set in Briox afterwards. Creates a new record only. POST /item.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | string | no | Item number; Briox picks the next free one when omitted. |
| description | string | yes | Item description (max 50 characters). |
| type | string | no | Goods or Service. |
| unit | string | no | Unit, for example st, h, each. |
| sales_account | string | no | Sales account, for example 3001. |
| vat_rate | number | no | VAT rate in percent, for example 25. |
| long_description | string | no | — |
| notes | string | no | — |
Create a customer invoice that is NOT posted (post=false): it is saved for review and the user posts and sends it in Briox. Needs an existing customer and at least one row. POST /customerinvoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The customer number (custno) from briox_list_customers. |
| invoice_date | string | no | Invoice date yyyy-mm-dd. |
| due_date | string | no | Due date yyyy-mm-dd. |
| currency | string | no | — |
| payment_term | string | no | Payment term id from briox_list_payment_terms. |
| your_reference | string | no | — |
| our_reference | string | no | — |
| invoice_text | string | no | Text shown on the invoice. |
| rows | array | yes | Invoice rows. |
- 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 Briox 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 |
|---|---|---|
| briox_get_company_info | no tags | |
| briox_list_customers | no tags | |
| briox_list_suppliers | no tags | |
| briox_list_customer_invoices | no tags | |
| briox_list_supplier_invoices | no tags | |
| briox_list_items | no tags | |
| briox_get_customer | no tags | |
| briox_get_supplier | no tags | |
| briox_get_customer_invoice | no tags | |
| briox_get_supplier_invoice | no tags | |
| briox_get_item | no tags | |
| briox_list_accounts | no tags | |
| briox_list_financial_years | no tags | |
| briox_list_journal_series | no tags | |
| briox_list_journals | no tags | |
| briox_get_journal | no tags | |
| briox_get_bank_account_balances | no tags | |
| briox_list_vat_codes | no tags | |
| briox_list_payment_terms | no tags | |
| briox_list_projects | no tags | |
| briox_list_cost_centers | no tags | |
| briox_list_sales_orders | no tags | |
| briox_create_customer | state-write | state-write: declares readOnlyHint: false |
| briox_create_item | state-write | state-write: declares readOnlyHint: false |
| briox_create_customer_invoice | state-write | state-write: declares readOnlyHint: false |
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
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.1.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 Briox 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.