# One OpenAPI operation, one MCP tool

This is a synthetic, local-only documentation example. It is not a generic
OpenAPI converter, hosted service or production authorization implementation.
It makes no API requests and uses no credentials. Values are illustrative,
not DocsAlot plan limits or customer data.

Place `openapi.json` and `server.mjs` in the same new folder. In that folder:

```bash
npm init -y
npm install @modelcontextprotocol/server@2.4.0 zod@4.6.7
node server.mjs
```

The process speaks MCP over stdio; it does not open an HTTP page or print a
human-readable greeting. Configure a compatible local MCP client to launch
`node` with the absolute path to `server.mjs`. Close the process with Ctrl+C
when running it directly in a terminal.

Expected tool: `get_public_plan`. Inputs are `starter` or `team`. The example
returns a synthetic export limit and an example.com source URL. The
`createAdminKey` operation is deliberately absent from the tool list.

Before adapting this to a real API, implement identity and tenant checks,
input/output validation, a fixed upstream destination, timeouts, safe errors,
rate limits, logging and an explicit read/write approval policy. Read-only
tool annotations are hints, not an authorization boundary.
