# saas-mcp-connector: a safe MCP server for a SaaS API

> An open-source MCP server for a SaaS API: per-user scoping, confirmed writes, read-only mode and rate limits, in TypeScript. Source and design notes.

Canonical: https://app369.com/case-studies/saas-mcp-connector/
Last updated: 2026-10-13

An MCP server that lets Claude Desktop, Claude Code and other MCP clients use a SaaS product's API safely. Every call is scoped to one user's workspace, writes need explicit confirmation, and the HTTP transport is rate limited.

**Simon’s role:** Open source, written by App369 founder Simon Dziak and released under the MIT license. It is a reference build that runs against an in-memory fake SaaS, not a client project and not a production deployment.

[saas-mcp-connector on GitHub](https://github.com/SzymonDziak/saas-mcp-connector) [MCP server for your SaaS, fixed price](https://app369.com/fixed-price/mcp-server-for-saas/)

The problem

## **What saas-mcp-connector Needed to Solve **

Customers are starting to ask whether a product works with their AI assistant. The easy way to build that is to expose the API as tools and hope the model behaves. The harder questions are the ones this build answers. Can a tool reach another customer's data? Can the model change something without asking? What happens when a client floods the server with requests, or when the upstream API fails with a message that should not reach the model?

The build

## **How It Was Built**

A TypeScript server on the official MCP SDK. Each token is resolved to an API client that is already bound to one workspace, and no tool takes a workspace argument, so cross-workspace access cannot be expressed. Write tools do nothing without confirm: true, and READ_ONLY=true blocks them completely. The same server runs over stdio for Claude Code and Claude Desktop, or over stateless Streamable HTTP with bearer-token auth and a per-token rate limit. The API client is an interface, so swapping the fake SaaS for a real REST API does not change the server.

Features

## **What the Product Does**

### **Six tools**

list_projects, list_tasks (with filters and cursor pagination), get_task and search are read tools. create_task and update_task_status are write tools.

### **Per-user scoping**

The token chooses the workspace. Tests cover reads, search, listing and writes across workspaces.

### **Read-only mode**

READ_ONLY=true makes every write tool return an error, even with confirm: true.

### **Explicit confirmation**

A write without confirm: true does nothing and tells the model to ask the user first.

### **Rate limiting**

A token bucket per token on the HTTP transport. Over the limit, the server returns 429 with Retry-After. Buckets are keyed by a hash of the token.

### **Safe errors**

Known failures come back as MCP tool errors with a readable message. Unexpected exceptions are logged to stderr and returned as a generic message, with no stack traces or upstream details.

Architecture

## **The Stack, Layer by Layer**

LayerWhat it does<dl>

<dt>**Server**</dt>
<dd>Node 22 or newer, TypeScript, the official @modelcontextprotocol/sdk and zod for input validation. Read tools carry readOnlyHint so clients can treat them differently.</dd>

<dt>**API layer**</dt>
<dd>An ApiClient interface in src/api.ts, an in-memory multi-workspace fake in src/fake-saas.ts, and a client factory that maps a token to a client.</dd>

<dt>**Transports**</dt>
<dd>stdio, and Streamable HTTP built fresh per request from the caller's token, so no session state can leak between users.</dd>

<dt>**Tests**</dt>
<dd>vitest suites that run offline: server logic, the HTTP transport and a stdio smoke test.</dd>
</dl>

By the numbers

## **Verifiable Facts**

**Oct 2026**

Published on GitHub (single commit, October 12)

**6**

Tools: 4 read and 2 write

**18**

Test cases across 3 test files

**MIT**

License

Counted from the public GitHub repository on October 13, 2026. This page makes no claims about stars, adoption or production use.

Lessons

## **What Simon Learned Shipping It**

2. 01 ### **Make the unsafe call impossible to write** The server does not check that a tool is allowed to name a workspace. No tool has the argument at all. Removing the option is easier to test than policing it.
3. 02 ### **Gate writes twice** Confirmation protects against a model that acts too fast. Read-only mode protects against a deployment that should never write. They answer different questions, so both exist.
4. 03 ### **Stay stateless on HTTP** Building a fresh server per request from the caller's token means there is no session to leak, and the process can be restarted or scaled without a sticky session.
5. 04 ### **Keep the API as the authority** The README says your own API must still enforce authorization. This layer is defense in depth, not the only lock.
6. 05 ### **Say what is not built** OAuth sign-in is described in the README as an optional extension and is not implemented. A short list of what is missing is more useful to the next reader than a long list of claims.

Technologies Used

- TypeScript
- Node.js
- MCP
- zod
- vitest
- Claude

Timeline

**Published October 2026**

Keep reading

## **More Case Studies**

[SaaS / Business software<h3>**Workspace369: a Flutter and Firebase SaaS for client work**</h3>An all-in-one workspace for freelancers and small service businesses: CRM, proposals, invoicing and payments, scheduling, a shared email/SMS/voice inbox, accounting and AI, in one Flutter app on iOS and the web. **Read Case Study **](https://app369.com/case-studies/workspace369/) [Field service software / Contractor CRM<h3>**QuoteIQ: a contractor CRM in Flutter, Nuxt and Firebase**</h3>A CRM for home service contractors: quotes, scheduling, invoices and payments, customer messaging and AI automations, on iOS, Android and the web. QuoteIQ is the client's app: on the App Store since September 2022, it is rated 4.7 from 3,400+ App Store ratings. **Read Case Study **](https://app369.com/case-studies/quoteiq/) [Consumer / Music<h3>**3693: a private music app in Flutter and Firebase**</h3>A private music app built with Flutter: search, a now-playing screen with lyrics, a queue, playlists, liked songs, a cloud library, listening stats and light and dark themes, on a typed Firebase backend. **Read Case Study **](https://app369.com/case-studies/3693-music-app/) [iOS app / Mobile navigation<h3>**Workspace369’s iPhone tab bar: native Liquid Glass, measured to the point**</h3>The bar at the bottom of an iPhone app is the first thing people touch. This is how Simon made Workspace369’s look and feel like Apple’s own, and how measuring instead of guessing found a hidden 15-point overlap. Under the hood: Apple’s native Liquid Glass tab bar on iOS 26 and later, with a Flutter-drawn twin on older iOS, Android and the web. **Read Case Study **](https://app369.com/case-studies/workspace369-tab-bar/)

## **Want something similar at a fixed price?**

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

- [**Web App MVP Sprint**from $6,000A scoped web app MVP in Vue/Nuxt or React, with a fixed quote after a $450 written scoping.](https://app369.com/fixed-price/web-app-mvp/)
- [**App Fix Ticket**from $450One reproducible bug in an existing mobile or web app, diagnosed and fixed.](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
- [**Monthly Dev Subscription**from $1,495/⁠monthOne development request at a time, most back in about 2 business days. Pause or cancel anytime.](https://app369.com/fixed-price/monthly-dev-subscription/)

Start here

## **Planning Something Similar?**

Simon builds Flutter and Firebase apps for startups and small businesses. Get a ballpark with the [app cost calculator](https://app369.com/tools/app-cost-calculator/), see [Flutter development](https://app369.com/service/flutter-development/), or tell him about your project.

[**Get in Touch **→](https://app369.com/contact/) [**See the Portfolio**](https://app369.com/portfolio/)