We're live in beta — earn up to 12,000 credits by signing up today. Get started

AroFlo MCP
for AI agents

FloConnector is a hosted AroFlo MCP server. Securely connect Claude, ChatGPT and other AI clients to AroFlo. Ask in plain English; it runs the 72 tools for you, behind one endpoint, with you deciding what it can touch.

Beta. Connect it today and every tool below is live. It is new enough that we are still testing it against real AroFlo accounts, so tell us if something looks off and we will fix it fast.

Built in-house. We wrote this connector ourselves and call AroFlo directly, with no third party in the path. Nothing in a request or response is retained by anyone but AroFlo.

Single connection. One AroFlo organisation per workspace. Connect another in a separate workspace.

Tools

Everything your AI can do in AroFlo

72 tools your agent gets the moment AroFlo is connected.

72 tools

  • list_changes read

    List what changed

    The change feed: which records changed and when, across every entity. FREE — the only AroFlo zone exempt from the site's 2,000-a-day request limit. Use this to decide what to fetch instead of re-listing whole zones.

  • list_tasks read

    List tasks

    List jobs (AroFlo calls them tasks), filtered by client, business unit, status, dates or job number. Use `join` to pull labour, materials, notes or totals into the SAME request rather than making a second one.

  • get_task read

    Get one task

    Fetch one job by its AroFlo ID, optionally with its labour, materials, notes, documents, location and totals attached. Draws on AroFlo's separate by-id request budget rather than the main daily one.

  • create_task write

    Create a task

    Create a job. Client, business unit, task type and due date are REQUIRED and cannot be changed afterwards through the API, so get them right the first time.

  • update_task write

    Update a task

    Update a job's name, contact, customer order number, status or substatus. AroFlo does NOT allow the client, business unit, task type, due date or description to be changed through the API.

  • list_task_labours read

    List labour lines

    Labour booked against jobs, as lines rather than whole tasks. Use this for cross-job questions (hours by date, by job, verified or locked); use aroflo_get_task with join=labour for one job's labour.

  • list_task_materials read

    List material lines

    Materials used on jobs, as lines rather than whole tasks. Use this for cross-job questions (usage by date, what has not been ordered or invoiced); use aroflo_get_task with join=material for one job.

  • list_task_expenses read

    List expense lines

    Expenses recorded against jobs, as lines rather than whole tasks. Read-only at AroFlo.

  • add_task_material write

    Add a material to a task

    Record a material used on a job. Always send `item` (the description) — a part number alone stores a line called "Parts" and does NOT link it to inventory or move stock. Taking stock from a store or a person requires `takenFromId`.

  • update_task_material write

    Update a material on a task

    Change the quantity, cost, markup, sell price or description of a material line already on a job. Requires both the line ID and the task ID.

  • add_task_resource write

    Assign a resource to a task

    Assign a user or a business unit to a job as a resource.

  • list_task_types read

    List task types

    The job types configured for this site. Read-only, and needed before creating a task: `create_task` requires a task type ID. Cached for ten minutes.

  • list_substatuses read

    List substatuses

    The custom substatuses configured for tasks and quotes. Read-only, and needed to set one on a task. Cached for ten minutes.

  • list_projects read

    List projects

    Projects, which group related jobs. Read-only at AroFlo.

  • list_project_stages read

    List project stages

    The stages within projects. Read-only at AroFlo.

  • list_quotes read

    List quotes

    Quotes, filtered by status, acceptance, job number or date. Read-only at AroFlo: v1 has no way to create, change or send a quote. Use `join` to pull line items or notes into the same request.

  • list_quote_line_items read

    List quote line items

    The line items on quotes. Read-only at AroFlo.

  • list_invoices read

    List invoices

    Customer invoices, filtered by status, invoice date, due date or the linked job's dates. Use `join` to pull line items, the task or notes into the same request.

  • update_invoice write

    Update an invoice

    Change an invoice's description or approval status. WARNING: setting the status to Processed also ARCHIVES the linked job in AroFlo, removing it from normal job lists. v1 cannot create invoices.

  • list_payments read

    List payments

    Payments recorded against invoices. Read-only at AroFlo.

  • list_purchase_orders read

    List purchase orders

    Purchase orders, filtered by status, supplier invoice number, purchase date, due date or delivery date. Use `join` to pull line items or the linked job into the same request.

  • update_purchase_order write

    Update a purchase order

    Change a purchase order's delivery instructions, delivery date or approval status. AroFlo allows nothing else on a PO through v1, and cannot create one.

  • list_bills read

    List supplier bills

    Supplier bills, filtered by status, purchase order, work order or dates. Use `join` to pull line items, notes or the linked jobs into the same request.

  • create_bill write

    Create a supplier bill

    Raise a supplier bill against a purchase order or a work order. One of those two is required. This is the only financial document v1 lets you create.

  • update_bill write

    Update a supplier bill

    Change a bill's number, description, dates or approval status.

  • list_bill_line_items read

    List bill line items

    The line items on supplier bills.

  • add_bill_line_item write

    Add a line to a supplier bill

    Add a line item to a supplier bill: order code, description, quantity, price and tax.

  • update_bill_line_item write

    Update a line on a supplier bill

    Change a bill line's code, description, quantity, price or tax. Requires both the line ID and the bill ID.

  • list_transaction_terms read

    List transaction terms

    The payment terms configured for this site. Read-only, and cached for ten minutes.

  • list_clients read

    List clients

    Customers, filtered by name, archived state or creation date. Use `join` to pull their locations, contacts, custom fields or priorities into the same request.

  • create_client write

    Create a client

    Create a customer. AroFlo requires a business name AND a contact person's first name and surname; state and country are required on the address.

  • update_client write

    Update a client

    Change a customer's name, contact details, addresses, payment terms, business units or posting flag.

  • list_client_notes read

    List client notes

    Notes recorded against customers.

  • create_client_note write

    Add a note to a client

    Record a note against a customer. The visibility filter is required and controls who sees it: internal staff, the client, contractors, or everyone.

  • update_client_note write

    Update a client note

    Change a note's text, visibility or pinned state. The content is required even when only changing visibility.

  • list_contacts read

    List contacts

    People at customers and contractors. Read-only at AroFlo: contacts are created through the client or supplier record.

  • list_locations read

    List locations

    Site addresses belonging to clients, suppliers or business units, filtered by owner, name, suburb, state or coordinates. Read-only at AroFlo.

  • list_suppliers read

    List suppliers

    Suppliers, filtered by name, archived state or creation date. Use `join` to pull their locations, contacts or custom fields into the same request.

  • create_supplier write

    Create a supplier

    Create a supplier. Like clients, AroFlo requires a business name AND a contact person's first name and surname.

  • update_supplier write

    Update a supplier

    Change a supplier's name, contact details, addresses, payment terms, business units or posting flag.

  • list_inventory read

    List inventory items

    Stocked items, filtered by part number, description or category. Add `join=stocklevels` to get on-hand quantities in the SAME request rather than making a second one.

  • create_inventory_item write

    Create an inventory item

    Add a stocked item. Part number, cost, maximum cost, sell price and category are all required by AroFlo. This creates the catalogue entry, not stock on a shelf.

  • update_inventory_item write

    Update an inventory item

    Change a stocked item's part number, description, costs, sell price, margin or category.

  • move_stock write

    Move stock

    Adjust how much of an item a business unit, person or store holds. `moveQuantity` is a CHANGE, not a new total: send 10 against a holder with 4 and they end up with 14. Use a negative number to remove.

  • list_inventory_stock_levels read

    List stock levels

    On-hand quantities per holder, for questions like "what is on this van?". For a single item's levels, prefer aroflo_list_inventory with join=stocklevels.

  • list_inventory_categories read

    List inventory categories

    The inventory category tree. Read-only, needed before creating an item, and cached for ten minutes.

  • list_inventory_lists read

    List inventory lists

    Saved item lists: task-specific kits, assemblies and schedule-of-rates lists. Add `join=items` to include their contents in the same request. Read-only.

  • list_custom_holders read

    List custom holders

    The named stores stock can be assigned to (warehouses, vehicles). Read-only, needed to move stock to one, and cached for ten minutes.

  • list_assets read

    List assets

    Equipment tracked in AroFlo, filtered by name, category, serial number or customer reference. Use `join` to pull the asset's location or custom fields into the same request.

  • create_asset write

    Create an asset

    Register a piece of equipment. Asset name, order code and category are required. Business unit and client cannot be changed later.

  • update_asset write

    Update an asset

    Change an asset's name, codes, serial number, odometer, cost, quantity or category. The owning business unit and client are fixed.

  • list_asset_categories read

    List asset categories

    The asset category tree. Read-only, needed before creating an asset, and cached for ten minutes.

  • list_schedules read

    List schedules

    Who and what is booked when. Filter by job, by the user or asset scheduled, or by start date. Add `join=archived` to include cancelled bookings.

  • create_schedule write

    Schedule a job

    Book a user or an asset onto a job for a time window. Dates use SLASHES on this zone (2026/08/04), unlike the rest of AroFlo.

  • list_timesheets read

    List timesheets

    Hours booked by users, filtered by job, person, work date or type (productive, non-productive, expense). Read-only: v1 cannot write timesheets.

  • list_work_orders read

    List work orders

    Work sent to contractors, filtered by number, internal status, contractor acceptance or dates. Use `join` to pull line items, the linked jobs or bills into the same request.

  • create_work_order write

    Create a work order

    Send work to a contractor. The job and the location are required; the contractor cannot be changed afterwards.

  • update_work_order write

    Update a work order

    Change a work order's location, required-by date, description or approval status. `status` is REQUIRED on every update — AroFlo fails the whole call without it. The job and contractor are fixed.

  • list_work_order_line_items read

    List work order line items

    The line items on work orders. Read-only at AroFlo.

  • list_priorities read

    List priorities

    Response-time priorities, which can be per business unit or per client. Needed before creating a job with a priority. Cached for ten minutes.

  • create_priority write

    Create a priority

    Add a response-time priority to a business unit or client. Response time is a type plus a value, not minutes. The owner must have `usecustompriorities` true, or AroFlo reports success and creates nothing — check that first, and confirm with a read after.

  • update_priority write

    Update a priority

    Change a priority's number, descriptions, response time, list order, colour or archived state.

  • list_business_units read

    List business units

    The site's business units — the `orgid` that creating a task, asset or priority requires. Read-only, and cached for ten minutes.

  • list_users read

    List users

    Staff on this AroFlo site, filtered by name, position or archived state. Add `join=permissiongroups` to see what each can do. Cached for ten minutes.

  • update_user write

    Update a user's contact details

    Change a staff member's name, email, phone or fax. Cannot change position, username, password, permission groups or business units.

  • list_permission_groups read

    List permission groups

    The permission groups defined on this site. Read-only at AroFlo, and cached for ten minutes.

  • list_user_positions read

    List user positions

    The position titles defined on this site. Read-only at AroFlo, and cached for ten minutes.

  • list_tracking_centres read

    List tracking centres

    Cost or tracking centres used for reporting. Cached for ten minutes.

  • list_message_board read

    List message board notes

    Notes posted to the site's internal message board. Read-only at AroFlo.

  • list_message_templates read

    List message templates

    Saved email and SMS templates. Cached for ten minutes.

  • create_message_template write

    Create a message template

    Save a reusable message template with a name, subject, body and format.

  • list_documents read

    List documents and photos

    Files in the site's document directory, filtered by name, comment or category. WARNING: the download links AroFlo returns expire after ten minutes, so use them immediately and never store them.

Questions, answered

How do I connect AroFlo to Claude?

Create a FloConnector workspace, connect AroFlo once from the dashboard, then add your FloConnector endpoint to Claude as a custom connector. Claude handles the sign-in prompt; there is no server to host and no code to write. The same endpoint works in ChatGPT.

What can Claude do in AroFlo?

72 tools: 43 that read AroFlo data and 29 that change it. Every tool is listed on this page, so you can see exactly what the model is able to call before you connect.

Does the AI see my AroFlo password or API keys?

No. FloConnector holds the AroFlo credential, encrypted before it is stored, and calls AroFlo on the model's behalf. The AI client only ever sees the tools and their results, never the credential behind them.

Can I stop it changing anything in AroFlo?

Yes. Each connection is exposed through a profile, and a profile carries only the tools you switch on. Leave the 29 write tools off and the connection is read-only.

Does this work with ChatGPT as well as Claude?

Yes. The endpoint is a standard hosted MCP server, so it works in any client that supports MCP connectors, including Claude and ChatGPT.