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 server | Hosted server | |
|---|---|---|
| How users connect | Install it, put an API key in a config file | Paste one URL, sign in in the browser |
| Where the key lives | On the user's machine | Encrypted on the server, never in the client |
| Works in web clients such as claude.ai | No | Yes |
| Who runs it | Each user | You, 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
- Less Annoying CRM, hosted: 50 automated tests, and a 20-step live test passing against the production server. Listed on PyPI and the official MCP registry.
- Brand data sample: a TypeScript server that serves a design system to assistants, with 24 of 24 evaluation questions answered correctly by a real MCP client against the hosted endpoint.
Both are our own projects, not client work. The Less Annoying CRM server is independent and not affiliated with that company.