Dev.to WebDev 🛠 Dev 👁 0 📖 2 min read

Let Claude and ChatGPT Run Your Coworking Space: What We Learned Adding MCP to a Small SaaS

Operators of small coworking spaces ask the same questions all day. "How full are we on Friday?" "Who has not paid?" "Book Anna a desk for Monday." We build OhMyDesk, a coworking management tool. This month we let opera

Operators of small coworking spaces ask the same questions all day. "How full are we on Friday?" "Who has not paid?" "Book Anna a desk for Monday."

We build OhMyDesk, a coworking management tool. This month we let operators ask these questions from Claude and ChatGPT. We used MCP (Model Context Protocol). Here is what we learned.

Why MCP and not another chat box

Operators already use an AI assistant. A new chat box in our app is one more tab to open. With MCP, the assistant they already use can call our tools. We do not build the chat UI.

Three rules we kept

1. Read first, write later. The first version only read data: occupancy, bookings, revenue. Reads cannot break anything. Writes came after.

2. Propose, then confirm. When the assistant wants to change data, it first shows a plan. "Cancel 3 bookings for Monday." The operator says yes or no. Only then does the change happen. This is the same pattern we use in our in-app Autopilot.

3. Use the same permissions as the app. The assistant gets the operator's role, nothing more. A staff member cannot read owner-only numbers through a chat.

A small thing that mattered: tool names

Models pick tools by name and description. Our first names were vague, like get_data. The assistant often chose the wrong one. We switched to plain names like list_bookings_for_date and short descriptions with one example. Wrong picks dropped a lot.

Slack as a second door

Many teams live in Slack. We added a Slack DM version of the same assistant. Same tools, same confirm step. The work was small because the tools already existed.

Side features that shipped with it

  • Coupons that can make a desk free, for guests and community days.
  • A custom tax label, because "VAT" is not the right word in every country.

What we would tell you

  • Start with read-only tools.
  • Keep the confirm step for every write.
  • Name tools like you name a good function.
  • Reuse your app permissions.

If you run a small space and want to try this, see OhMyDesk. The AI features are in the changelog. You can also book a short demo.

📰 Read the original article on Dev.to WebDev

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