Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Bilflo 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 Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bilflo-mcp-by-usefulapi https://bilflo.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# bilflo_list_clients, bilflo_get_client, bilflo_list_client_contacts and 23 more
Bilflo 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 bilflo-mcp-by-usefulapi https://bilflo.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.
26 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 staffing company's clients (the customers contractors are placed with): id, business name, client code, phone, active flag. Each row carries the number of addresses and contacts; set include_details for the full address and contact lists. Bilflo returns every client at once, so this tool filters and pages the list itself. GET /v1/Clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only clients whose business name or client code contains this text (case-insensitive). |
| active_only | boolean | no | Only active clients. |
| include_details | boolean | no | Include each client's addresses and contacts (large; use with a small limit). |
| limit | integer | no | Rows to return, 1-200 (default 50). |
| offset | integer | no | Rows to skip (default 0). Bilflo does not page, so the list is cut here. |
One client with its addresses and contacts. GET /v1/Clients/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id (from bilflo_list_clients). |
The contacts (people at the client: name, title, phone, email, active flag) of one client. GET /v1/Clients/contact/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
The addresses (work sites and billing addresses) of one client. GET /v1/Clients/addresses/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
The agreements (billing terms) on file for one client. GET /v1/Clients/agreements/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
The contract purchase orders of one client (PO numbers and amounts used for billing). GET /v1/Clients/contractPOs/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
The contract invoice groups of one client (which jobs are invoiced together). GET /v1/Clients/contractInvoiceGroups/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
One contract job (a contractor placed with a client): client, contractor, title, start/end dates, status, overtime rule, timecard method, per-diem/expense/sick-time flags, workers' comp code and burden. GET /v1/ContractJobs/{jobId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
The pay and bill rates (pay/bill items such as Regular, Overtime) of one contract job. GET /v1/ContractJobs/{jobId}/payBillItems.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
Who approves the timecards of one contract job. GET /v1/ContractJobs/{jobId}/approvers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
The purchase orders attached to one contract job. GET /v1/ContractJobs/{jobId}/purchaseOrders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
The custom field values of one contract job. GET /v1/ContractJobs/{jobId}/customFields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
One direct hire (a permanent placement): header, fee/split data, contacts and custom fields as Bilflo returns them. GET /v1/DirectHires/{jobId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo direct hire job id. |
One contractor: profile (name, email, phone, address, W2/1099), jobs, checks paid, work status, benefit settings and custom fields. Social security number, date of birth and bank details are removed from the reply. GET /v1/Users/contractors/{contractorId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contractor_id | integer | yes | Bilflo contractor id. |
One back-office team member (staffing company user): profile, roles and compensation settings. Government ids and bank details are removed. GET /v1/Users/teamMember/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_member_id | integer | yes | Bilflo team member (user) id. |
The company's overtime rules (id, name, state). Use the ids with bilflo_update_contract_job. GET /v1/OvertimeRules.
No parameter schema on file.
One of the company's lookup lists: workers_comp_codes, payment_terms, remittances, burden_settings, benefit_rules, states or pay_bill_items. GET /v1/CompanySettings/{setting}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setting | string | yes | Which list to read. |
The company's custom fields (active and inactive) with type, requiredness per service offering and, for list fields, the selectable items. GET /v1/CustomFields.
No parameter schema on file.
The selectable items of one custom list field (id from bilflo_list_custom_fields). Items of a field named like personal data (SSN, date of birth, bank account, password) are not shown. GET /v1/CustomFields/items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| custom_field_id | integer | yes | Custom field id (from bilflo_list_custom_fields). |
Run one of the company's saved custom reports and return its rows. Report parameters are report specific key/value pairs, for example {"Start": "2026-01-01", "End": "2026-01-31"}. Reads data only. POST /v1/Reports/{reportId}/Execute.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | integer | yes | Bilflo custom report id. |
| parameters | object | no | Report parameters as key/value pairs. |
WRITE: creates a new client (customer) in Bilflo with the given business name and returns its id. It is visible to the whole staffing company and used for billing, so check bilflo_list_clients first to avoid a duplicate. POST /v1/Clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | Business name of the new client. |
WRITE: changes only the client fields you pass (business name, client code, phone, fax, active flag); the rest stay as they are. Setting is_active=false deactivates the client. PATCH /v1/Clients/{clientId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
| business_name | string | no | — |
| client_code | string | no | — |
| phone | string | no | — |
| fax | string | no | — |
| is_active | boolean | no | false deactivates the client, true reactivates it. |
WRITE: changes only the contract job fields you pass (title, overtime rule, workers' comp code, burden, per-diem/expenses/sick-time/meal-period flags); the rest stay as they are. Pay and bill rates change payroll and invoices, so confirm values with the user. Client, contractor, dates and status cannot be changed here. PATCH /v1/ContractJobs/{jobId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
| job_title | string | no | — |
| overtime_rule_id | integer | no | Overtime rule id (bilflo_list_overtime_rules). |
| workers_comp_code_id | integer | no | Workers' comp code id (bilflo_get_company_setting workers_comp_codes). |
| burden_manual | number | no | Manual burden value. |
| is_per_diem_enabled | boolean | no | — |
| is_sick_time_enabled | boolean | no | — |
| is_expenses_enabled | boolean | no | — |
| is_waive_meal_period | boolean | no | — |
| is_allow_skip_lunch | boolean | no | — |
WRITE: ends a contract job on the given date (the contractor stops being placed with the client; no more timecards are expected after it). Affects payroll and invoicing. A terminated job can be brought back with bilflo_reopen_contract_job. POST /v1/ContractJobs/terminate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
| end_date | string | yes | Last day of the job, yyyy-mm-dd. |
WRITE: reopens a terminated contract job (like the Open Job button): the job becomes active again, the end date is cleared, the contractor is made active and the missing timecards from the reopen date's week are created. Fails if the job is not terminated or the company plan has no room for another active job. POST /v1/ContractJobs/{jobId}/reopen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
| reopen_date | string | yes | Date to reopen from, yyyy-mm-dd (not before the job start). |
WRITE: changes only the contractor contact fields you pass (name, title, email, phone, address, company); the rest stay as they are. Tax, bank, social security number and activation are not changeable here. PATCH /v1/Users/contractors/{contractorId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contractor_id | integer | yes | Bilflo contractor id. |
| first_name | string | no | — |
| middle_name | string | no | — |
| last_name | string | no | — |
| title | string | no | — |
| email_address | string | no | — |
| phone | string | no | — |
| phone_ext | string | no | — |
| address1 | string | no | — |
| address2 | string | no | — |
| city | string | no | — |
| zip_code | string | no | — |
| state_code | string | no | Two-letter state code. |
| contractor_company | string | no | The contractor's own company name (1099). |
- 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 Bilflo 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 |
|---|---|---|
| bilflo_list_clients | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_client | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_client_contacts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_client_addresses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_client_agreements | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_client_contract_pos | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_client_invoice_groups | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_contract_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_job_pay_bill_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_job_approvers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_job_purchase_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_job_custom_fields | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_direct_hire | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_contractor | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_team_member | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_overtime_rules | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_get_company_setting | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_custom_fields | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_list_custom_field_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_run_report | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| bilflo_create_client | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bilflo_update_client | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bilflo_update_contract_job | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bilflo_terminate_contract_job | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| bilflo_reopen_contract_job | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| bilflo_update_contractor | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, 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.18.0.
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 Bilflo 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.