Do we need to change our API?

Usually not. The server runs on your existing API and OAuth. If you only have API keys, a hosted sign-in page handles the user connection.

Local or remote MCP server?

Remote, for customers. They connect it by URL or from a directory in Claude, ChatGPT or Grok without installing anything.

You do. It lives in your GitHub and hosting accounts.

Can we see it working before we commit?

Yes. The free demo is built from your public API docs and a trial or sandbox account, never published, and deleted after 14 days.

Build an MCP server for your SaaS

Updated October 21, 2026

The short answer

An MCP server lets Claude, ChatGPT, Grok and other assistants call your product's API for a signed-in user.

For a SaaS company the production version is a remote server on your own domain, using your OAuth, with a focused set of tools your customers actually ask for.

What a production build includes

Remote MCP server over HTTPS (Streamable HTTP) at mcp.yourcompany.com
Your existing OAuth, or a hosted sign-in page if you only have API keys
Up to 15 tools, each with a clear name, description and read-only or destructive annotation
Tests in Claude, ChatGPT and Grok, plus a 20-prompt eval suite
Written security note, runbook and connect guide
Code in your GitHub, deployed in your Cloudflare or Vercel account

Choosing the tools

Start from the questions your customers ask, not from your endpoint list. Read the objects they look up most, then add a few safe write actions, such as drafting instead of publishing.

Our demo builds follow this: who is working today and draft an open shift (Deputy), parts below minimum stock (MaintainX), deliveries still unassigned (Onfleet). Built from public docs; not clients, not affiliated.

What you provide

API sandbox and key
Hosting access (Cloudflare or Vercel)
A DNS record for the server
Your OAuth app, if you run your own
A reviewer test account with sample data, for directory submissions

How long it takes

10 business days from when API access, hosting and DNS are in. Directory review happens after that, and each platform sets its own timing.

Questions

Do we need to change our API?: Usually not. The server runs on your existing API and OAuth. If you only have API keys, a hosted sign-in page handles the user connection.
Local or remote MCP server?: Remote, for customers. They connect it by URL or from a directory in Claude, ChatGPT or Grok without installing anything.
Who owns the code?: You do. It lives in your GitHub and hosting accounts.
Can we see it working before we commit?: Yes. The free demo is built from your public API docs and a trial or sandbox account, never published, and deleted after 14 days.