Companies

The team and billing container: admins, members, associated projects and closure reversible for 30 days.

  • Category: Projects and companies
  • Status: Available
  • Requirements: An ArduMaker account with an active session; To manage members: be an admin of the company
  • MCP tools (Read only): listar_empresas, ver_empresa, ver_estado_verificacion_empresa, listar_servicios_empresa, ver_consumo_periodo_empresa

Markdown

What can you do with it?

The company is the container for everything that is contracted and paid for in ArduMaker: VPS, domains, email, AI keys and associated projects. Each company has admins and members.

  • Create a company: whoever creates it becomes a member and an admin.
  • Add people by username, as a member or as an admin.
  • Promote or demote someone between admin and member.
  • Remove members, or leave the company yourself.
  • Close the company and restore it from the trash for 30 days.

When should you use it?

  • To keep billing for different clients or businesses apart.
  • To give a team access to the projects associated with that company.
  • So an MCP agent can discover the company_id other tools require.

How does it work in ArduMaker?

  1. On creation, ArduMaker validates the name, adds the creator as member and admin, and registers it as a customer in the payment processor. It all happens in one transaction: if the payment registration fails, no half-created company is left behind.
  2. Every admin is also a member: if someone who was not a member is made admin, they are added to the members.
  3. Only an admin adds people, changes roles or removes others. Any member can leave on their own.
  4. A company is never left without an admin: demoting or removing the last admin is rejected.

Deleted companies are not listed, with one exception: those closed for non-payment remain visible so their owner can still log in and pay.

What actually changes?

  • Create: a new company with its creator as admin and its customer in the payment processor.
  • Associating the company with a project gives its members (level aportar) and admins access to that project.
  • Closing: any pending debt is charged first; the company is marked as deleted and stays 30 days in the trash. Its VPS are actually deleted and do not come back on restore.

Diagram

  1. Person: asks to create the company
  2. Validation: name and debts in other companies
  3. Company: creator as member and admin
  4. Payment processor: customer registration, in the same transaction
Creating a company

Expected result

The company appears in the list of its creator and members, and can be associated with projects and used to contract services.

Errors and troubleshooting

MessageCause
name is requiredCreation was attempted without a name.
Cannot create a new company while having 2 or more companies with pending debtsThe person has two or more companies with debt above the authorized limit. A single one does not block.
Only admins can add membersThe person trying to add someone is not an admin.
At least one admin is requiredAn attempt was made to remove or demote the last admin.
Cannot remove members while company has pending debtsThe company owes more than authorized.
Company has pending debts and cannot be deletedThe charge before closing did not cover the debt.

MCP access

An MCP agent sees the companies of the person who authorized it, with summary fields. All tools are read-only: an agent does not create companies, add members or close anything.

  • listar_empresas: id, name, status and the person's role in each one.
  • ver_empresa: profile, admins and members, without billing data.
  • ver_estado_verificacion_empresa: whether the company is verified, without the tax data.
  • listar_servicios_empresa and ver_consumo_periodo_empresa: active services and balance movements.

Full reference for each tool: /mcp/docs.

Related features