Local services & SaaS
Petpooja
Sales, menu items, stock and online orders across your Petpooja outlets.
11 endpoints
TMBill publishes no public API for its restaurant POS and backoffice (checked 15 Nov 2026). Cotlet runs a hosted TMBill MCP server with 3 read tools that ChatGPT and Claude use in your own backoffice: outlet reports, inventory and staff. Nothing is billed, changed or deleted.
3 tools Read only
TMBill publishes no public API documentation, API keys or API pricing for its restaurant POS and backoffice. No TMBill MCP server and no official ChatGPT or Claude connector was found.
| What you need | Merchant app | Backoffice by hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your outlets | Not available | Copy and paste | Hosted MCP server |
| Reports, inventory and staff | On your phone | Report by report | 3 read tools |
| A summary waiting at 8 every morning | Only when you open it | Only when you log in | n8n or cron over REST |
Checked 15 Nov 2026. Sources: TMBill home · TMBill products · TMBill backoffice sign-in · TMBill Merchant on the App Store
Once, in a browser we host for you.
One address in its settings.
Sales, stock and staff, outlet by outlet.
Your agent works in your own signed-in Cloud Browser and only reads. It sees the outlets your TMBill login sees. Who can see your session
Sign in to TMBill in a Cloud Browser. Open backoffice.tmbill.com in your Cotlet Cloud Browser, pick Company or Management, and sign in with your password or an emailed OTP.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
TMBill is reached through the shared address https://cotlet.dev/mcp/v1, like every other app you turn on, so one connector covers them all. Turned TMBill on later? Refresh the connector for its 3 tools.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: tmbill_read The three areas TMBill names for owners: reports and outlet performance, inventory tracking and staff management. Each tool reads and runs at once.
One outlet or all of them, for a day or a range, side by side.
Returns the figures of the chosen report, as text, outlet by outlet, in your account currency. With several outlets or franchise locations on one login, it puts them side by side. It changes nothing and runs without asking.
MCP calltmbill_read → view_outlet_reports
REST endpointGET https://cotlet.dev/api/v1/tmbill/outlet-reports/view
| Name | Type | Description |
|---|---|---|
| report string | string | Report name as the backoffice lists it under Reports. Leave empty for the outlet summary. |
| outlet string | string | Outlet name as TMBill shows it. Leave empty for every outlet your login can open. |
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to `from`. |
{
"from": "2026-11-14"
} {
"report": "Outlet summary",
"from": "2026-11-14",
"to": "2026-11-14",
"outlets": [
{
"outlet": "Example Cafe, Main Street",
"orders": 312,
"sales": 98450
},
{
"outlet": "Example Cafe, Station Road",
"orders": 241,
"sales": 76210
},
{
"outlet": "Example Cafe, Mall",
"orders": 188,
"sales": 61930
}
]
} Stock on hand per item and outlet, and who works where.
Returns each stock item with its quantity and unit as TMBill records them. TMBill runs inventory together with recipe and wastage management. Read only: the agent records no purchase, transfer or wastage.
MCP calltmbill_read → track_inventory
REST endpointGET https://cotlet.dev/api/v1/tmbill/inventories/track
| Name | Type | Description |
|---|---|---|
| outlet string | string | Outlet name as TMBill shows it. Leave empty for every outlet your login can open. |
| item string | string | One stock item or a part of its name. Leave empty for the whole list. |
{
"outlet": "Example Cafe, Main Street",
"items": [
{
"item": "Milk",
"quantity": 18,
"unit": "l"
},
{
"item": "Coffee beans",
"quantity": 6.5,
"unit": "kg"
},
{
"item": "Paneer",
"quantity": 3,
"unit": "kg"
}
]
} Returns each staff member with their outlet and role as TMBill shows them. Read only: no user is added, removed or given new rights.
MCP calltmbill_read → view_staff
REST endpointGET https://cotlet.dev/api/v1/tmbill/staffs/view
| Name | Type | Description |
|---|---|---|
| outlet string | string | Outlet name as TMBill shows it. Leave empty for every outlet your login can open. |
{
"staff": [
{
"name": "Staff member A",
"outlet": "Example Cafe, Main Street",
"role": "Captain"
},
{
"name": "Staff member B",
"outlet": "Example Cafe, Main Street",
"role": "Cashier"
},
{
"name": "Staff member C",
"outlet": "Example Cafe, Mall",
"role": "Manager"
}
]
} Your signed-in TMBill backoffice profile, AES-256-GCM encrypted, in Finland. Never your password.
The 3 TMBill read tools. The session cookie stays in the Cloud Browser.
The outlets, reports, stock and staff your Company or Management login can open.
Billing at the till, menus and prices, purchases, user rights, payment gateways and delivery platform links.
You sign in again yourself, in the same Cloud Browser.
Disable TMBill for agents, reset the browser, or change your TMBill password.
Cotlet never sees or stores your password. You type it yourself, or the OTP TMBill emails you, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the TMBill server when TMBill changes its backoffice, so your morning summary keeps arriving without a change on your side.
The agent sees the outlets your TMBill login sees. A login limited to one outlet gives the agent that outlet only.
If TMBill signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Area | Who handles it |
|---|---|
| Billing and orders | Your staff, on the TMBill POS |
| Menus, prices and recipes | You, in the backoffice |
| Purchases, transfers, wastage | Your store manager, in inventory |
| Users and rights | You, in the backoffice |
All 3 tools read and run at once, without a confirmation. None of them bills an order, records stock or changes a user.
{
"name": "view_outlet_reports",
"arguments": {
"from": "2026-11-14"
}
} curl "https://cotlet.dev/api/v1/tmbill/outlet-reports/view?from=2026-11-14" \
-H "Authorization: Bearer $COTLET_API_KEY" {
"report": "Outlet summary",
"from": "2026-11-14",
"to": "2026-11-14",
"outlets": [
{
"outlet": "Example Cafe, Main Street",
"orders": 312,
"sales": 98450
},
{
"outlet": "Example Cafe, Station Road",
"orders": 241,
"sales": 76210
},
{
"outlet": "Example Cafe, Mall",
"orders": 188,
"sales": 61930
}
]
} The example reads the outlet summary for 14 November across three outlets: 741 orders in all. A cron job or n8n flow can make the same call over REST at /api/v1/tmbill with the same key and price, in JSON, and post the result to your team chat. Failed calls are free.
About $16 a monthfor a chain of three outlets with a daily summary and stock check, 2,800 credits. Your TMBill plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning outlet summary | 1 × 30 | 300 |
| Stock check, three outlets | 3 × 30 | 900 |
| Week-on-week outlet comparison | 2 × 4 | 80 |
| Staff lists | 1 × 2 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 130 calls | 2,800 |
The smallest pack, 5,000 credits for $29, covers this month. Each extra outlet adds about one stock check a day.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| TMBill Merchant app | Reports, outlet performance, inventory and staff on an iPhone or iPad. | You open it and read it yourself. |
| TMBill backoffice | Every report and setting, in a browser. | One report at a time, while you are logged in. |
| TMBill's own integrations | Direct links from the POS to delivery platforms, payment gateways and accounting. | They move orders and money between systems; they do not answer questions. |
If TMBill publishes an API that covers your reports, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script reading TMBill today, from your own backoffice login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the TMBill tools.
Sign up free at https://cotlet.dev/signup?app=tmbill, turn on TMBill under Integrations in the console and sign in at https://backoffice.tmbill.com/ in your Cloud Browser. Then connect your AI agent and ask it how your outlets did yesterday. The trial needs no card.
TMBill publishes no public API documentation, API keys or API pricing for its restaurant POS and backoffice (checked 15 Nov 2026). No TMBill MCP server and no official ChatGPT or Claude connector was found; TMBill advertises direct integrations of its own POS instead. Cotlet does not need one: it reads your own signed-in TMBill backoffice.
No. The three TMBill tools only read: outlet reports, inventory and staff. Billing, menus, prices, purchases and user rights stay in TMBill, where you and your staff handle them.
The backoffice login that sees the outlets you want reported, under Company or Management on backoffice.tmbill.com. The agent sees what that login sees, so an outlet manager's login gives reports for that outlet only.
The TMBill backoffice offers English and Arabic. The tools return the names and figures your backoffice shows, and you can ask your agent in either language.
Only in how it is called. Both carry the same 3 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with TMBill or Techmainstay Software Private Limited.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy