A
licenseB
qualityB
maintenanceEnables managing invoices, estimates, customers, and dashboard/account data in a self-hosted invoicing system through 23 MCP tools, while automatically handling undocumented required API fields on writes.
23
MIT
Bilflo MCP by usefulapi
by io.usefulapi
Server Details
Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
A3.5/5.0
Scored across 26 tools
Disambiguation5/5
Each tool targets a clearly distinct resource and action; client-level vs job-level purchase orders, custom fields, and pay/bill items are well separated by their descriptions. No two tools appear to duplicate the same operation.
Naming Consistency5/5
All tools follow the same bilflo_ prefix plus snake_case verb_noun convention. Verbs such as list, get, create, update, terminate, reopen, and run are used consistently across resources.
Tool Count3/5
At 26 tools, the surface is above the typical 3-15 range and enters the heavy zone. Many tools earn their place as granular subresource reads for a complex staffing domain, but the set still feels broad for the actions exposed.
Completeness2/5
The set covers many reads and some updates, but major core workflows are missing: no list_contract_jobs, no list_contractors, no create_contract_job/direct_hire/contractor, and no timecard, payroll, or invoicing operations. These gaps would block common agent tasks in a Bilflo staffing back office.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read work orders, customers and invoices; create customers, notes and work orders in FieldEdge.
Read staff, projects, clients, time, expenses and invoices; create time entries in BigTime.
Read clients, offers and invoices; create clients and offer drafts in Billify.
Read Bill4Time clients, projects, time entries, expenses, invoices, payments, users and contacts.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables freelancers and agencies to run eight back-office workflows across Stripe, Google Drive, Linear, Google Calendar, Gmail, GitHub, Google Docs, Granola, Google Sheets and Firecrawl, covering client onboarding, invoices from calendar and commits, status reports, scope-creep detection, site audits and overdue invoice chasers. Reads run freely, while anything that creates, sends, changes or deletes is shown for approval first, with credentials kept in your own OS keychain and no proxying through any third-party server.28Apache 2.0
- AlicenseAqualityCmaintenanceConnects Claude-compatible clients to Freelancer.com so users can search and bid on projects, read and send messages, review bids and projects, and manage skills or specialty profiles. Supports multiple Freelancer accounts switchable per tool call.2152 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and change jobs, job status, customers, quotes with line items, invoices, quote and invoice email, payments, and Scheduler bookings in an account by reusing the user's own signed-in Chrome session, with no official API keys needed. Ships read-only hints and confirmation prompts for tools that reach other people, and can be run over stdio or streamable HTTP.222403 PyPI6Elastic 2.0
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.