Bilflo MCP by usefulapi
io.usefulapi/bilflo · v1.4.0 · MCP 2025-06-18
Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them.
Reachability
reachable
checked 2026-10-26 05:31 UTC
Registry status active
Tools pinned 26
09c781eda9d7
Tools last changed
unchanged since first capture 2026-10-25
Repo last push 2026-10-26
as of 2026-10-26
GitHub stars 0
as of 2026-10-26
Provenance
Registry namespace io.usefulapi
(domain verified by the official registry)
Repository
github.com/m190/usefulapi-mcp
Website
https://usefulapi.io/bilflo/
Remote endpoints
https://bilflo.usefulapi.io/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-10-25 05:30 | first capture | 26 tools pinned |
Pinned tool definitions (26)
| Tool | Description |
|---|---|
| bilflo_list_clients | 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... |
| bilflo_get_client | One client with its addresses and contacts. GET /v1/Clients/{clientId}. |
| bilflo_list_client_contacts | The contacts (people at the client: name, title, phone, email, active flag) of one client. GET /v1/Clients/contact/{clientId}. |
| bilflo_list_client_addresses | The addresses (work sites and billing addresses) of one client. GET /v1/Clients/addresses/{clientId}. |
| bilflo_list_client_agreements | The agreements (billing terms) on file for one client. GET /v1/Clients/agreements/{clientId}. |
| bilflo_list_client_contract_pos | The contract purchase orders of one client (PO numbers and amounts used for billing). GET /v1/Clients/contractPOs/{clientId}. |
| bilflo_list_client_invoice_groups | The contract invoice groups of one client (which jobs are invoiced together). GET /v1/Clients/contractInvoiceGroups/{clientId}. |
| bilflo_get_contract_job | 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}. |
| bilflo_list_job_pay_bill_items | The pay and bill rates (pay/bill items such as Regular, Overtime) of one contract job. GET /v1/ContractJobs/{jobId}/payBillItems. |
| bilflo_list_job_approvers | Who approves the timecards of one contract job. GET /v1/ContractJobs/{jobId}/approvers. |
| bilflo_list_job_purchase_orders | The purchase orders attached to one contract job. GET /v1/ContractJobs/{jobId}/purchaseOrders. |
| bilflo_get_job_custom_fields | The custom field values of one contract job. GET /v1/ContractJobs/{jobId}/customFields. |
| bilflo_get_direct_hire | One direct hire (a permanent placement): header, fee/split data, contacts and custom fields as Bilflo returns them. GET /v1/DirectHires/{jobId}. |
| bilflo_get_contractor | 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... |
| bilflo_get_team_member | 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}. |
| bilflo_list_overtime_rules | The company's overtime rules (id, name, state). Use the ids with bilflo_update_contract_job. GET /v1/OvertimeRules. |
| bilflo_get_company_setting | 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}. |
| bilflo_list_custom_fields | The company's custom fields (active and inactive) with type, requiredness per service offering and, for list fields, the selectable items. GET /v1/CustomFields. |
| bilflo_list_custom_field_items | 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. |
| bilflo_run_report | 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. |
| bilflo_create_client | 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. |
| bilflo_update_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}. |
| bilflo_update_contract_job | 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... |
| bilflo_terminate_contract_job | 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 | 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... |
| bilflo_update_contractor | 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... |
Get alerted when this changes.
Email the moment io.usefulapi/bilflo drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.usefulapi/bilflo)
Maintain this server? Add the badge to your README. It links your users to this live status page.