[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# TMBill API and MCP server: Let your AI agent read every outlet before you open.

> 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.

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.

- Free 7-day trial, no card
- Unofficial, not affiliated with TMBill
- Page: https://cotlet.dev/integrations/tmbill-api-mcp-server

## What can your AI agent do in TMBill?

- Send yesterday's sales per outlet
- Compare outlets week on week
- List stock on hand before the supplier order
- List the staff of an outlet

## Does TMBill have an MCP server or an API?

- TMBill advertises "Direct Integrations with Our POS": it connects to delivery platforms, payment gateways and accounting itself.
- Owners read reports, outlet performance, inventory and staff in the backoffice or in the TMBill Merchant app for iPhone and iPad.
- TMBill says 14,000+ restaurants in 35+ countries run on it, from single outlets to chains of 100+.

| 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](https://tmbill.com/), [TMBill products](https://tmbill.com/products), [TMBill backoffice sign-in](https://backoffice.tmbill.com/), [TMBill Merchant on the App Store](https://apps.apple.com/us/app/tmbill-merchant/id6744350961)

## How does the TMBill MCP server work?

1. **Sign in to TMBill.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Ask about your outlets.** 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.

## How to connect TMBill to your AI agent

1. **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.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. **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.

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Claude:

```
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:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: tmbill_read
```

## All 3 TMBill MCP tools

The three areas TMBill names for owners: reports and outlet performance, inventory tracking and staff management. Each tool reads and runs at once.

### Reports and outlet performance

One outlet or all of them, for a day or a range, side by side.

- **View outlet performance reports** (`view_outlet_reports`, read): Read a TMBill report for one outlet or all of them, for a day or a date range.

### Inventory and staff

Stock on hand per item and outlet, and who works where.

- **Track restaurant inventory** (`track_inventory`, read): Read stock on hand per item and outlet from TMBill inventory.
- **View restaurant staff** (`view_staff`, read): List the staff of one outlet or all outlets, as the backoffice shows them.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/tmbill-api-mcp-server#tools

## Who can see my TMBill session, and how do I revoke it?

- **What we store.** Your signed-in TMBill backoffice profile, AES-256-GCM encrypted, in Finland. Never your password.
- **What your agent gets.** The 3 TMBill read tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** The outlets, reports, stock and staff your Company or Management login can open.
- **What no tool touches.** Billing at the till, menus and prices, purchases, user rights, payment gateways and delivery platform links.
- **If TMBill signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** 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](https://cotlet.dev/security.md)).

## What happens when TMBill changes?

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.

## Read only: what the agent leaves alone

1. **You ask.** Yesterday's sales, best outlet first.
2. **The agent reads.** view_outlet_reports opens the outlet summary.
3. **It sorts and sums.** In the chat, not in TMBill.
4. **You decide.** Orders, prices and staff stay your call.

| 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.

MCP call:

```
{
  "name": "view_outlet_reports",
  "arguments": {
    "from": "2026-11-14"
  }
}
```

REST:

```
curl "https://cotlet.dev/api/v1/tmbill/outlet-reports/view?from=2026-11-14" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Response:

```
{
  "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.

## How much does the TMBill MCP server cost?

**About $16 a month** for 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.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your TMBill plan and login apply as they are

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

## TMBill MCP server: other ways to connect

| 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.

## Who runs Cotlet

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.

## TMBill MCP server: questions

### How do I get access?

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.

### Does TMBill have an API?

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.

### Can the agent bill orders or change prices in TMBill?

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.

### Which TMBill login should I use?

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.

### Does the agent work in Arabic?

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.

### Is the MCP server different from the REST API?

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.

### Is Cotlet affiliated with TMBill?

No. Cotlet is independent and not affiliated with TMBill or Techmainstay Software Private Limited.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
