The MCP server lets you connect an AI assistant, such as Claude Code, to the system. From your assistant you can then look up any record, register incomes, expenses and loans, group movements into transfers, and compare a bank statement with what is registered, by asking for it in your own words. The assistant works with your account: everything it changes is recorded under your name.
Who can use it
MCP is in the side menu of the admin panel. To reach the panel, open the menu at the top right and choose Go To Admin Panel. Only super administrators see the entry and can open the page; anyone else gets a 405 error page.
If your account is blocked, deactivated or deleted, every token you created stops working straight away.
Turn the server on
The server starts Off: while it is off, every call is rejected, whatever token it brings.
- Open MCP.
- In MCP server, click Turn on. You see MCP server turned on and the status changes to On.
The switch is shared: it turns the server on or off for every super administrator. Click Turn off to reject every token at once, without deleting any of them, until someone turns it on again.
Create a token
A token is the key your assistant uses to get in. Create one for each place you connect from, so you can remove one without affecting the others.
- In Your tokens, write a name that tells you where you will use it, such as Claude Code on my laptop.
- Click Create token.
- Copy your token now appears with the token. Click Copy token and keep it somewhere safe.
- Click Done.
The token is shown only this once. If you lose it, regenerate it.
The table lists your tokens with their Name, when they were Created and when they were Last used (Never until your assistant first connects). On a phone, the table shows only the Name and the actions, so Regenerate and Revoke stay in reach. You only see your own tokens.
Connect Claude Code
Connection shows the Server URL of this system, and the Claude Code command already filled in with it. Copy that command, put your token in place of <token>, and run it in your computer's terminal:
claude mcp add --transport http weblabor-admin <server URL> --header "Authorization: Bearer <token>"
Then open Claude Code and ask it something about the system, for example the expenses paid this month. Another assistant connects with the same Server URL, sending the token in the header shown under Header.
Regenerate or revoke a token
- Regenerate gives you a new value for the token, under the same name. The old value stops working at once, so update your assistant with the new one.
- Revoke asks you to confirm, then deletes the token. Anything connected with it stops working right away, and you see Token revoked.
Ploi and licences
Your assistant can also do the server application and licence work you would otherwise do screen by screen:
- Deploy an application on Ploi. It runs the same checks as Execute on Ploi and answers with the same message when one fails, such as a server without a Ploi ID or a project without a repository. When nothing stops it, the deploy is requested: it runs in the background, and your assistant can ask how it is going, step by step, as the deploy monitor shows it.
- Give people access to an application's database. It runs the same check as Ploi User Sync, for that application only, and later tells you how many people were added. Access nobody expects is kept, as on the screen.
- Compare an application's .env with the env defaults. It tells you which keys are missing, which differ and which are secret, without ever showing a value. It can then write the defaults that are not secret; secret keys are never read or written.
- Report on licences. For a day (today unless you say otherwise) it lists the licences ending soon, the ones already expired, the sites the next nightly run would suspend, and the production applications with no hosting licence, which are never suspended.
- Renew a licence. The end date moves one year forward, or to the date you give, and the start date stays. If the licence had suspended a site, the site is resumed. A cancelled licence cannot be renewed, and a licence that has not ended yet is only renewed when you confirm it, so the same payment is not counted twice.
When Ploi is busy and limits requests, your assistant says so instead of waiting; ask again in a minute.
Finance actions
Your assistant can also do the finance actions of the panel and the pay tool, with the same rules:
- Split an expense. It splits one charge into two or more expenses, such as one per domain, and links each to its licence. The parts must add up exactly to the total; if they do not, it tells you the difference. An expense that is already paid or already in a transfer is not split, as on the screen.
- Finish a loan. It marks the loan as finished, as Mark as Finished does. If payments are still pending, the loan is finished anyway and your assistant lists them. A loan that is already finished is left as it is.
- Move money between sprints. It does what Transfer Money does on a sprint, with the same list of sprints it can send money to. It is not a bank transfer.
- Add a commission to a sprint. It adds the seller's commission and the expense that pays it, as Add Commission does. The seller must have the Vendedor role.
- Register salaries and team payments. One person or several at once. Before writing, your assistant shows you what it would register, and nothing is written until you confirm. Several payments are registered together or not at all. A person with no position, or with no salary on that date, is refused, and a payment that looks already registered is pointed out before anything is written. As in the pay tool, you say which bank account the money goes out from, and each person gets one transfer for everything paid to them; the preview shows those transfers too.
Confirming the final validation of a transfer stays with you: your assistant cannot do it.
Portfolio and blog
Your assistant can write the works of the portfolio and the blog articles of weblabor.mx, as described in Portfolio and blog:
- Write an entry. It writes it in Spanish and says whether it is a draft or published in the same step. The other languages of the site are translated by themselves in the background, and your assistant tells you how many translations it asked for.
- Add its image. It uploads the image first, from its address on the internet or as a small file, and then uses it in the entry. Only JPEG, PNG, GIF and WebP images are taken, up to 10 MB from an address or 2 MB as a file; anything else is refused with the reason.
- Change or delete an entry. It tells you how many translations a change asked for again, or how many were deleted with it.
- Check languages. It does what the Check languages button does: it asks for every translation missing in a language of the site.
What your assistant can and cannot do
- It reaches every module of the system with your super administrator access, and its changes follow the same rules as the screens. When the system rejects a change, your assistant is told why.
- Every amount is in Mexican pesos (MXN).
- Nothing stops it from registering the same movement twice. Ask it to check first when you are not sure something is already registered.
- Comparing a bank statement only reports the difference; it changes nothing. Paid movements that belong to no transfer are listed from every bank account, because they are not tied to one.
- It never sees passwords, PINs, database passwords, the values of the Ploi env tool or people's contracts: they show as [hidden]. It cannot reach tokens or the server's own switch, and it can read the activity history but not change it.
- Everything it changes appears in the activity history under your name, marked as done through the MCP.