Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect TouchBistro to Claude Code

Pull shift reports and, where your plan allows, edit menu items in TouchBistro. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect TouchBistro to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect TouchBistro, you add a TouchBistro MCP server: a small hosted service that exposes TouchBistro's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own TouchBistro account. No API keys pasted into config files.

claude mcp add --transport http touchbistro https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in TouchBistro once connected?

Full read-write access lets Claude update menu items and modifiers, adjust prices, toggle availability, and pull sales and labor reports on request, then apply changes once you approve. The menu edits and end-of-day pulls that meant clicking through the POS happen where your restaurant data already lives, with you confirming each write.

  • Update a menu item name, description, or price after you approve it
  • Toggle items or modifiers as available or 86'd for a shift
  • Adjust modifier groups and pricing on a menu category
  • Pull a sales summary or item-level report for a date range
  • Create or edit a menu item within an existing category
  • Flag low-selling items from a report for a menu review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same TouchBistro access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the TouchBistro API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when TouchBistro changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build TouchBistro connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same TouchBistro connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own TouchBistro account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on TouchBistro's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to TouchBistro?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the TouchBistro account it signs in with. Revoking access is one click in TouchBistro.

More on the TouchBistro connector

TouchBistro connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us