Dev.to AI 🤖 Ai 👁 0 📖 4 min read

How to connect Petpooja to AI agents over MCP

Petpooja has no MCP server and publishes no API documentation or API keys page for restaurants. Checked 31 Oct 2026. The route for ChatGPT, Claude or any other AI agent is Cotlet.dev, which works through your own Petpooj

Petpooja has no MCP server and publishes no API documentation or API keys page for restaurants. Checked 31 Oct 2026. The route for ChatGPT, Claude or any other AI agent is Cotlet.dev, which works through your own Petpooja login.

How the connection works

Cotlet.dev runs a single MCP server at https://cotlet.dev/mcp/v1. Your AI agent connects to that address and finds the Petpooja tools listed like any other MCP tools, even though Petpooja gives restaurants no API of its own.

Your AI agent calls a tool such as Get sales report. Cotlet.dev carries out the matching task inside Petpooja the way a person at the back office would, then hands the result back as the tool's answer. Reach is bounded by your login, so the rights you set in Petpooja decide what the agent can see and change.

Cotlet.dev is independent and not affiliated with Petpooja. If a built-in Petpooja integration already does what you need, start there.

Connection steps

Petpooja needs a real login, and the person who owns it types the password. Cotlet.dev never sees it. Follow these four steps:

  1. Sign up at Cotlet.dev.
  2. Sign in to Petpooja in the Cloud Browser. Use your own login at billing.petpooja.com, either an owner or a user whose rights cover reports, menu and inventory.
  3. Press Enable for agents on Petpooja.
  4. Add https://cotlet.dev/mcp/v1 as an MCP server in your agent, whether that is ChatGPT, Claude or any other client.

Petpooja lets you set rights user by user, so create a login limited to the outlets and screens the agent actually needs. For clients that read a JSON config file, the entry looks like this:

{"mcpServers": {"cotlet": {"url": "https://cotlet.dev/mcp/v1"}}}

Petpooja tools

Your AI agent gets eleven Petpooja tools, grouped here by area.

Outlets and reports

  • List outlets: each outlet with its name, city and whether online ordering is switched on.
  • Get sales report: daily sales, discounts and tax for a single outlet.
  • List bill exceptions: cancelled, discounted or modified bills and cash drawer operations, plus who performed them.
  • Get online order reconciliation: for each platform, the orders, order value, commission, charges, taxes and expected payout.

Menu and online ordering

  • List menu items: an outlet's items with category, price and online ordering status.
  • Set item availability: turn one menu item on or off for online orders.
  • Update item price: change what a menu item costs.
  • Set outlet online status: turn online ordering on or off for a whole outlet.

Stock and purchasing

  • List raw materials: current stock beside the low stock level.
  • List purchase orders: supplier, status and number of items.

Customers

  • List customers: CRM customers with visits, reward points and last visit.

Petpooja add-ons for kitchen display, captain ordering, the restaurant website and loyalty have no tool. Petpooja also documents no webhooks for owners, so the agent acts when you ask, not when something happens.

What waits for approval

Cotlet.dev separates the tools by what they touch. Reads go straight through, so reports, lists and reconciliation come back without a pause. Actions that reach other people or change money wait for the owner's OK in the Cotlet.dev console.

Your AI agent can propose a price change, and nothing happens in Petpooja until you approve it. Item switches and outlet online status change what customers can order, so expect to confirm those in the console too.

Petpooja states that menu edits, prices and item switches made in its POS carry over to the aggregators connected to your outlet. Cotlet.dev makes the change inside Petpooja the way you would, so the same carry-over applies. The agent cannot see the Swiggy or Zomato screens themselves.

Example agent run

Your AI agent can chain several tools from one plain request. Here is an illustrative run for a manager who asks, "Give me yesterday's picture and fix whatever ran out."

  1. Request: list outlets. Result: each outlet with name, city and online ordering status, so the agent knows where to look.
  2. Request: get the sales report for the main outlet. Result: sales, discounts and tax by day.
  3. Request: list bill exceptions. Result: cancelled and discounted bills, with the staff member behind each.
  4. Request: get online order reconciliation. Result: per platform orders, commission, charges, taxes and expected payout, which the agent sets against what the platform paid.
  5. Request: list raw materials. Result: current stock next to the low stock level, and the agent names the items below it.
  6. Request: set item availability to off for the dish that depends on the missing ingredient. Result: the call waits in the Cotlet.dev console. Once the owner approves, the item is off for online orders.

Your AI agent ran every step except the last without a pause, because those were reads.

More detail

Petpooja details, the full tool list and the MCP setup are on the Cotlet.dev Petpooja integration page, where you can check them against this post.

Cotlet.dev also has a walkthrough for owners that covers the same connection in plain language, without the MCP details.

Cotlet.dev belongs to Take Group sp. z o.o., a software company registered in Poland, EU. Questions about the Petpooja tools go to [email protected].

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.