Integration

Nibo Empresas integration

Nibo Empresas (Nibo Gestao Financeira) is a Brazilian financial management platform. An agent can manage customers, suppliers, employees and partners (socios); receipt and payment schedules (accounts receivable and payable) with categories, cost centers, recurrence and installments, settle them or record paid and received amounts; bank accounts, balances, statements, transfers and reconciliation items; boleto charges with Pix and NFS-e service invoices; categories, cost centers, annotations, budgets, users and organizations. Issuing an NFS-e or a charge, or a receipt schedule set to generate them, is a real fiscal or billing act. Lists take OData $filter, $orderby, $top (at most 500) and $skip; values are Portuguese. Not included: the file upload and the routes that need its file id (attach a file to a schedule, inbox item), the duplicate create routes that answer the full record, and contact updates: a contact's bank account number is withheld from every read, and an update sent without it could clear it. Authentication is the company's API token (in Nibo: the company, More options, Settings, API), sent in the ApiToken header; the API is offered on the Premium plan.

Connect Nibo Empresas How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Nibo Empresas.Built from the 84 Nibo Empresas tools below, on the connection you add once.

What you can do with Nibo Empresas

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Receipt schedule, 8 operations

create_receipt_scheduleCreate receipt schedulePOSTAgents: ask firstCreates a receipt schedule (stakeholderId, scheduleDate, dueDate, categories required). collection and autoGenerateNFSeType can issue a boleto charge and an NFS-e to the customer, immediately when set to do so.
delete_receipt_scheduleDelete receipt scheduleDELETEAgents: ask firstDeletes a receipt schedule. The answer is empty.
get_receipt_scheduleGet receipt scheduleGETAgents: ask firstReturns one receipt schedule by id: contact, value, dates, categories, cost centers, paid and open values, installment, recurrence and NFS-e status.
list_open_receipt_schedulesList open receipt schedulesGETAgents: ask firstLists the open (not fully received) receipt schedules, with customer, value, dates and categories. OData $filter, $orderby, $top (max 500), $skip.
list_overdue_receipt_schedulesList overdue receipt schedulesGETAgents: ask firstLists the overdue receipt schedules, with customer, value, dates and categories. OData $filter, $orderby, $top (max 500), $skip.
list_receipt_schedulesList receipt schedulesGETAgents: ask firstLists receipt schedules (accounts receivable): customer, value, due and accrual dates, categories, cost centers, paid and open values. OData $filter, $orderby, $top (max 500), $skip.
settle_receipt_scheduleSettle receipt schedulePOSTAgents: ask firstSettles (baixa) a receipt schedule: records an amount received on a date into a bank account (accountId), and returns the receipt id.
update_receipt_scheduleUpdate receipt schedulePUTAgents: ask firstUpdates a receipt schedule (stakeholderId, dueDate, scheduleDate, categories required): send every value back from get_receipt_schedule. It clears a boleto or NFS-e automation set at creation unless collection and autoGenerateNFSeType are sent again.

Payment schedule, 7 operations

create_payment_scheduleCreate payment schedulePOSTAgents: ask firstCreates a payment schedule (an account payable) for a supplier, employee or partner (stakeholderId, scheduleDate, dueDate, categories required), with optional recurrence or installments.
delete_payment_scheduleDelete payment scheduleDELETEAgents: ask firstDeletes a payment schedule. The answer is empty.
list_open_payment_schedulesList open payment schedulesGETAgents: ask firstLists the open (not fully paid) payment schedules, with contact, value, dates and categories. OData $filter, $orderby, $top (max 500), $skip.
list_overdue_payment_schedulesList overdue payment schedulesGETAgents: ask firstLists the overdue payment schedules, with contact, value, dates and categories (the docs list no filter or paging parameter for this route).
list_payment_schedulesList payment schedulesGETAgents: ask firstLists payment schedules (accounts payable): supplier, value, due and accrual dates, categories, cost centers, paid and open values. OData $filter, $orderby, $top (max 500), $skip.
settle_payment_scheduleSettle payment schedulePOSTAgents: ask firstSettles (baixa) a payment schedule: records an amount paid on a date from a bank account (accountId), and returns the payment id.
update_payment_scheduleUpdate payment schedulePUTAgents: ask firstUpdates a payment schedule (stakeholderId, dueDate, scheduleDate, categories, costcenters required): read the schedule from list_payment_schedules and send its values back with the change. Empty answer.

Schedule, 6 operations

list_customer_schedulesList customer schedulesGETAgents: ask firstLists the receipt and payment schedules of one customer, with values, dates, categories and paid or open state. OData $filter, $orderby, $top (max 500), $skip.
list_employee_schedulesList employee schedulesGETAgents: ask firstLists the schedules of one employee, with values, dates, categories and paid or open state. OData $filter, $orderby, $top (max 500), $skip.
list_installment_schedulesList installment schedulesGETAgents: ask firstLists the schedules of an installment plan: schedule id, due, expected and accrual dates, value and installment number.
list_partner_schedulesList partner schedulesGETAgents: ask firstLists the schedules of one partner (socio), with values, dates, categories and paid or open state. OData $filter, $orderby, $top (max 500), $skip.
list_schedulesList schedulesGETAgents: ask firstLists every receipt and payment schedule of the company: contact, value, dates, categories, cost centers, paid and open values. OData $filter, $orderby, $top (max 500), $skip.
list_supplier_schedulesList supplier schedulesGETAgents: ask firstLists the receipt and payment schedules of one supplier, with values, dates, categories and paid or open state. OData $filter, $orderby, $top (max 500), $skip.

Cost center, 5 operations

create_cost_centerCreate cost centerPOSTAgents: ask firstCreates a cost center (Description required). The docs show an empty answer; the new id is returned under id when Nibo sends it.
delete_cost_centerDelete cost centerDELETEAgents: ask firstDeletes a cost center. The answer is empty.
get_cost_centerGet cost centerGETAgents: ask firstReturns one cost center by id: description and last update.
list_cost_centersList cost centersGETAgents: ask firstLists the company's cost centers: id, description and last update. OData $filter, $orderby, $top (max 500), $skip.
update_cost_centerUpdate cost centerPUTAgents: ask firstUpdates a cost center's description (required: the update rewrites the record). Empty answer.

Customer, 4 operations

create_customerCreate customerPOSTAgents: ask firstCreates a customer (name required; CPF or CNPJ, contact details, address, bank details and company data optional) and returns its id.
delete_customerDelete customerDELETEAgents: ask firstDeletes a customer. The answer is empty.
get_customerGet customerGETAgents: ask firstReturns one customer by id: name, CPF or CNPJ, contact details, address, bank details and company data. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld).
list_customersList customersGETAgents: ask firstLists the company's customers: name, CPF or CNPJ, email, phone, address, bank and company data. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld). OData $filter, $orderby, $top (max 500), $skip.

Employee, 4 operations

create_employeeCreate employeePOSTAgents: ask firstCreates an employee (name required; CPF, contact details, address and bank details with Pix key optional). The docs show an empty answer; the new id is returned under id when Nibo sends it.
delete_employeeDelete employeeDELETEAgents: ask firstDeletes an employee. The answer is empty.
get_employeeGet employeeGETAgents: ask firstReturns one employee by id: name, CPF, contact details, address and bank details. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld).
list_employeesList employeesGETAgents: ask firstLists the company's employees: name, CPF, email, phone, address and bank details. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld). OData $filter, $orderby, $top (max 500), $skip.

Partner, 4 operations

create_partnerCreate partnerPOSTAgents: ask firstCreates a partner (socio) (name required; CPF, contact details, address and bank details with Pix key optional). The docs show an empty answer; the new id is returned under id when Nibo sends it.
delete_partnerDelete partnerDELETEAgents: ask firstDeletes a partner (socio). The answer is empty.
get_partnerGet partnerGETAgents: ask firstReturns one partner (socio) by id: name, CPF, contact details, address and bank details. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld).
list_partnersList partnersGETAgents: ask firstLists the company's partners (socios): name, CPF, email, phone, address and bank details. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld). OData $filter, $orderby, $top (max 500), $skip.

Supplier, 4 operations

create_supplierCreate supplierPOSTAgents: ask firstCreates a supplier (name required; CPF or CNPJ, contact details, address, bank details with Pix key and company data optional) and returns its id.
delete_supplierDelete supplierDELETEAgents: ask firstDeletes a supplier. The answer is empty.
get_supplierGet supplierGETAgents: ask firstReturns one supplier by id: name, CPF or CNPJ, contact details, address, bank details and company data. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld).
list_suppliersList suppliersGETAgents: ask firstLists the company's suppliers: name, CPF or CNPJ, email, phone, address, bank and company data. Personal data (CPF/CNPJ, contacts, bank and branch; the account number is withheld). OData $filter, $orderby, $top (max 500), $skip.

Bank account, 3 operations

create_bank_accountCreate bank accountPOSTAgents: ask firstCreates a bank account for the company (name required). The docs show an empty answer; the new id is returned under id when Nibo sends it. The API offers no route to delete an account.
list_bank_accountsList bank accountsGETAgents: ask firstLists the company's bank accounts: name, opening balance and date, type, bank branch and account number, archive and automation flags. OData $filter, $orderby, $top (max 500), $skip.
update_bank_accountUpdate bank accountPUTAgents: ask firstUpdates a bank account (Name and DateOfOpenBalance required). Nibo rewrites the whole account and empties what is left out: read it with list_bank_accounts and send every value back with the change. Empty answer.

Category, 3 operations

create_categoryCreate categoryPOSTAgents: ask firstCreates a schedule category in a group (categoryGroupId, name and type in or out required) and returns its id. The API offers no route to edit or delete a category.
get_categoryGet categoryGETAgents: ask firstReturns one schedule category by id: name, type, group, subgroup and whether it can be edited.
list_categoriesList categoriesGETAgents: ask firstLists the categories available on the company's receipt and payment schedules: id, name, type and group. OData $filter, $orderby, $top (max 500), $skip.

Charge, 3 operations

cancel_chargeCancel chargePOSTAgents: ask firstCancels a charge (boleto with Pix) the customer may already have received.
create_chargeCreate chargePOSTAgents: ask firstCreates a charge (boleto with Pix) for a receipt schedule and notifies the debtor per deliveryType: a real billing act sent to the customer. ScheduleId, DueDate and CollectionProfileId are required.
list_chargesList chargesGETAgents: ask firstLists charges (boletos with Pix): debtor and beneficiary, schedule, value, due date, status, links to the charge and its PDF. Debtor data is personal data. OData $filter, $orderby, $top (max 500), $skip.

Payment, 3 operations

delete_paymentDelete paymentDELETEAgents: ask firstPermanently deletes a payment (settlement) of a payment schedule; it cannot be recovered. The answer is empty.
list_paymentsList paymentsGETAgents: ask firstLists the payments made (settled payables): entry id, schedule id, bank account, contact, categories, value and date. OData $filter, $orderby, $top (max 500), $skip.
record_paymentRecord paymentPOSTAgents: ask firstRegisters a payment to a supplier, employee or partner: Nibo creates a schedule and settles it from the given bank account with the amount paid, and returns the id.

Receipt, 3 operations

delete_receiptDelete receiptDELETEAgents: ask firstDeletes a receipt (settlement) of a receipt schedule. The answer is empty.
list_receiptsList receiptsGETAgents: ask firstLists the receipts received (settled receivables): entry id, schedule id, bank account, contact, categories, value and date. OData $filter, $orderby, $top (max 500), $skip.
record_receiptRecord receiptPOSTAgents: ask firstRegisters an amount received from a customer: Nibo creates a schedule and settles it into the given bank account, and returns the id.

Schedule annotation, 3 operations

create_schedule_annotationCreate schedule annotationPOSTAgents: ask firstAdds a text annotation (Body) to a schedule. Nibo accepts it even for a schedule id that does not exist, so check the schedule first (get_receipt_schedule or list_schedules).
delete_schedule_annotationDelete schedule annotationDELETEAgents: ask firstDeletes an annotation of a schedule.
list_schedule_annotationsList schedule annotationsGETAgents: ask firstLists the annotations of a schedule: id, text, creation date and author.

Service invoice, 3 operations

cancel_service_invoiceCancel service invoicePOSTAgents: ask firstCancels an issued service invoice (NFS-e): a fiscal act on a document the customer may already have received.
issue_service_invoiceIssue service invoicePOSTAgents: ask firstIssues a service invoice (NFS-e, the municipal electronic service invoice) for a receipt schedule (ScheduleId): a real fiscal document sent to the city hall, undone only by cancel_service_invoice.
list_service_invoicesList service invoicesGETAgents: ask firstLists the issued service invoices (NFS-e): status and messages, schedule, customer (personal data), service, taxes and values. OData $filter, $orderby, $top (max 500), $skip.

Transfer, 3 operations

create_transferCreate transferPOSTAgents: ask firstRecords a transfer of an amount between two of the company's bank accounts (origin, destination, date, value) as an entry in each, changing both balances in Nibo; delete_transfer removes it. The answer is empty.
delete_transferDelete transferDELETEAgents: ask firstDeletes a transfer between accounts: its records in the origin and destination accounts are deleted.
list_transfersList transfersGETAgents: ask firstLists transfers between the company's bank accounts: origin and destination entries with account, date, description and value. OData $filter, $orderby, $top (max 500), $skip.

Bank, 2 operations

get_bankGet bankGETAgents: ask firstReturns one bank by id: code, name, color, bank number and automation flags.
list_banksList banksGETAgents: ask firstLists the banks available for a bank account: id, code, name, bank number and automation flags. Use the id as bankId in create_bank_account.

Receipt schedule file, 2 operations

delete_receipt_schedule_fileDelete receipt schedule fileDELETEAgents: ask firstDeletes a file attached to a receipt schedule. The answer is empty.
list_receipt_schedule_filesList receipt schedule filesGETAgents: ask firstLists the files attached to a receipt schedule: file id, name, creation date and size. OData $filter, $orderby, $top (max 500), $skip.

Reconciliation item, 2 operations

delete_reconciliation_itemDelete reconciliation itemDELETEAgents: ask firstPermanently deletes a reconciliation item of a bank account; it cannot be undone.
list_reconciliation_itemsList reconciliation itemsGETAgents: ask firstLists the bank entries of an account waiting for reconciliation, with the entry and Nibo's suggested mapping.

Account balance, 1 operation

list_account_balancesList account balancesGETAgents: ask firstReturns the balance of each of the company's accounts with its bank details, pending reconciliations and bank balance. OData $filter, $orderby, $top (max 500), $skip.

Bank statement, 1 operation

get_bank_statementGet bank statementGETAgents: ask firstReturns the statement of one bank account between startDate and endDate (both required, YYYY-MM-DD): each entry's contact, description, value, date and running balance.

Budget, 1 operation

get_budgetGet budgetGETAgents: ask firstReturns the company's budget for a year: the planned value of each budget category, month by month.

Category group, 1 operation

list_category_groupsList category groupsGETAgents: ask firstLists the schedule category groups: id, name and reference code. OData $filter, $orderby, $top (max 500), $skip.

Category tree, 1 operation

get_category_treeGet category treeGETAgents: ask firstReturns the chart of categories as a tree: each group with its categories and subgroups, type (income or expense) and flags.

Collection profile, 1 operation

list_collection_profilesList collection profilesGETAgents: ask firstLists the collection (charge) profiles: name, fine and interest percentages, payment methods and notification settings. Their id is the CollectionProfileId of create_charge.

Contact, 1 operation

list_contactsList contactsGETAgents: ask firstLists every contact (customers, suppliers, employees, partners) with type, name, CPF or CNPJ and contact details: personal data. Filter on type, for example type eq 'Customer'.

Installment plan, 1 operation

get_installment_planGet installment planGETAgents: ask firstReturns an installment plan by id: whether the total is divided, number of installments and total value.

Organization, 1 operation

list_organizationsList organizationsGETAgents: ask firstLists the organizations (companies) the token's administrator user can access: name, CNPJ, plan, users (name and email), features and accountant.

Payment schedule file, 1 operation

delete_payment_schedule_fileDelete payment schedule fileDELETEAgents: ask firstDeletes a file attached to a payment schedule. The answer is empty.

Service profile, 1 operation

list_service_profilesList service profilesGETAgents: ask firstLists the service profiles set up in Nibo's NFS-e settings: name, description, service codes and tax rates. Their id is the serviceProfileId of NFS-e tools.

User, 1 operation

list_usersList usersGETAgents: ask firstLists the company's users: email (personal data), creation and invitation acceptance dates, owner, user and accountant flags, and roles. OData $filter, $orderby, $top (max 500), $skip.

Use Nibo Empresas from Claude Code, Cursor or Codex

Connect Nibo Empresas in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Nibo Empresas operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Nibo Empresas

Create your workspace
Sign up free. Nothing to install.
Connect Nibo Empresas once
Add your Nibo Empresas connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.