Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"bilflo": {
"url": "https://bilflo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"bilflo": {
"type": "http",
"url": "https://bilflo.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Bilflo API key and Company ID.
Create the API key on the Credentials page of developer.bilflo.com. The Company ID is the GUID your staffing company was given for the API (ask [email protected] if you do not have it). Your key is used only to call the Bilflo API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Bilflo API key and Company ID. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Bilflo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
bilflo_list_clients | read | 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 lists. Bilflo returns every client at once, so this tool filters and pages the list itself. GET /v1/Clients. |
bilflo_get_client | read | Get client One client with its addresses and contacts. GET /v1/Clients/{clientId}. |
bilflo_list_client_contacts | read | 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 | read | List client addresses The addresses (work sites and billing addresses) of one client. GET /v1/Clients/addresses/{clientId}. |
bilflo_list_client_agreements | read | List client agreements The agreements (billing terms) on file for one client. GET /v1/Clients/agreements/{clientId}. |
bilflo_list_client_contract_pos | read | 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 | read | 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 | read | 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 | read | 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 | read | List job approvers Who approves the timecards of one contract job. GET /v1/ContractJobs/{jobId}/approvers. |
bilflo_list_job_purchase_orders | read | List job purchase orders The purchase orders attached to one contract job. GET /v1/ContractJobs/{jobId}/purchaseOrders. |
bilflo_get_job_custom_fields | read | Get job custom fields The custom field values of one contract job. GET /v1/ContractJobs/{jobId}/customFields. |
bilflo_get_direct_hire | read | 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 | read | 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 /v1/Users/contractors/{contractorId}. |
bilflo_get_team_member | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | Run custom 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 | 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 | 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 | 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 confirm values with the user. Client, contractor, dates and status cannot be changed here. PATCH /v1/ContractJobs/{jobId}. |
bilflo_terminate_contract_job | write | 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. POST /v1/ContractJobs/terminate. |
bilflo_reopen_contract_job | write | 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 job is not terminated or the company plan has no room for another active job. POST /v1/ContractJobs/{jobId}/reopen. |
bilflo_update_contractor | write | Update contractor contact details 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}. |
bilflo_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
bilflo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Bilflo tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
bilflo_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Bilflo (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
bilflo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Bilflo Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run bilflo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Bilflo server only. Subscribe with bilflo_upgrade (it returns a Stripe Checkout link). Cancel any time with bilflo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running bilflo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Bilflo. The server calls the Bilflo API with your own Bilflo access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Bilflo API key and Company ID. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Bilflo API key and Company ID. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Bilflo API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Bilflo.
Yes, if you approve it. 6 of the 26 Bilflo tools can create or change data. The other 20 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Bilflo server only. Cancel any time: Pro then runs to the end of the paid period. Run bilflo_usage_status to see how many calls you used.
Ask the AI to run bilflo_upgrade: it returns a Stripe Checkout link. To cancel, run bilflo_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with bilflo_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.