Two front doors onto the same numbers: a dashboard you can read in this
browser, and an MCP endpoint at /mcp for an AI client.
Both answer under your own Erply rights, so what you see is what your Erply
user is allowed to see.
Operations — deliveries into your location and what
your customers owe.
Bookkeeping — transfers to key, and receivables.
Sign in to Erply — needed once a day before any panel
will answer.
/health answers {"ok":true} when it is.
You reaching this page already proves the load balancer, IAP and the server
are all working.
Point an MCP client at http://mcp.poolmarts.com/mcp.
A browser cannot do this — MCP is JSON-RPC with a session handshake.
| decides may you reach this at all | |
| Erply | decides what you may see — your own user's rights, so a store manager sees their own warehouse and no more |
Signing in to Google does not sign you in to Erply. Send your Erply username
and password to POST /signin, roughly weekly; the password is
exchanged for a session and never stored. /whoami says
where you stand.