MCP guide

How to give your SaaS product an official MCP server

By Northkeel Labs. Updated 21 November 2026.

An official MCP server turns your public API into tools that Claude, ChatGPT, Cursor and other assistants can use on a customer's behalf. Most of the work is not the code. It is choosing tools that match real tasks, getting sign-in right with OAuth 2.1 even if your API only has API keys, limiting what a read-only user can do, and treating everything your API returns as untrusted text.

This guide covers what goes into a production MCP server for a software product, the sign-in options, and what to check before you list it. It draws on two servers we built and run in public: a hosted server for Less Annoying CRM and a brand data sample.

Why an official server, not a community one

If you do not publish a server, someone else may. A community server usually asks your customers to paste an API key into a config file on their laptop, exposes whatever endpoints its author chose, and is not reviewed by you. An official server lets you decide which actions an assistant can take, what a read-only user can see, how fast it can call your API, and how to switch it off.

What goes into one

Tools that match real tasks, not every endpoint

Each tool is a task a user would ask an assistant to do, such as "find this contact" or "add a note", with a clear description and strict input checks. The Less Annoying CRM server has 10 tools: 6 that read and 4 that write, with no delete tools. Results are paged and long text fields are cut to a fixed length, so one call cannot flood the assistant.

Sign-in: OAuth 2.1, even if your API only has API keys

A hosted server is one URL that users paste into Claude, ChatGPT, Cursor or another client. The MCP specification builds sign-in on OAuth 2.1: the server publishes metadata (RFC 9728) that tells the client where to sign in, and the current version prefers Client ID Metadata Documents for client registration, keeping dynamic client registration for older clients.

If your API has only API keys, the server can bridge the two. The user signs in once in the browser and pastes their key on a consent page; the server checks the key against your API, stores it encrypted, and hands the client a short-lived token instead. The key never sits in the client's config. That is how the Less Annoying CRM server works, since that CRM has no OAuth of its own.

Access levels

Offer at least read-only and read-and-write. In the Less Annoying CRM server a read-only grant sees only the 6 read tools, and any call to a write tool is refused, whether or not the client listed it.

Treat your own data as untrusted

Text your API returns, such as a note a customer typed, reaches the assistant as input. Someone can write instructions into that text. The server cannot make that harmless, but it can label returned data as untrusted, cap its size, keep tool descriptions free of anything a third party controls, and keep a person in the loop for writes.

Rate limits, tests and a listing

Limit calls per user (the CRM server allows 60 per minute per grant), test every tool and every sign-in error path, and run a real MCP client against the deployed server before launch. Then list it where users look, such as the official MCP registry.

Local or hosted?

Local serverHosted server
How users connectInstall it, put an API key in a config filePaste one URL, sign in in the browser
Where the key livesOn the user's machineEncrypted on the server, never in the client
Works in web clients such as claude.aiNoYes
Who runs itEach userYou, or us on your behalf

Many products ship both: a local package for developers and a hosted URL for everyone else. Our Less Annoying CRM server exists in both forms, as a Python package on PyPI and as the hosted version.

Proof you can check

Both are our own projects, not client work. The Less Annoying CRM server is independent and not affiliated with that company.

Questions

Do we need OAuth if our API only uses API keys?

For a hosted server, yes, but you do not have to change your API. The server can run its own OAuth sign-in, take the key once on a consent page and store it encrypted, as our Less Annoying CRM server does.

Which assistants can use it?

Any client that supports remote MCP servers, including claude.ai custom connectors, Claude Desktop and Cursor. A local server works with desktop clients only.

Where does it run, and who owns it?

Where you choose: your cloud, or ours in your region. You own the code. Monthly care is optional.

What does it cost?

A server with a handful of core tools starts as a Starter project, from USD 99. A hosted server with OAuth is a bigger build, quoted in writing after a free demo on your public API.

Want a demo on your API first?

Send us your API docs link. We build a working demo server and send you a short video of it in use.

Get a free demo

Or write to contact@northkeellabs.com