Your first MCP tool call
Start with Node + stdio and a local MCP client. No account is required. The bundled examples call a mock API on your own computer.
- Clone the mcpmint repository, then run
node scripts/demo-api.mjswith Node 22 or later. Keep that terminal running. Checkhttp://127.0.0.1:8787/ping. - Download an example below and import it. Select the GET tool. Choose the Local Claude Desktop preset on Export. You can also select Claude Code in the installation wizard.
- Download and extract the archive. In its folder run
npm install, thennpm run build. Copy.env.exampleto.env. Fill the required credentials for the bearer example. - Enter the extracted folder’s absolute path in the wizard. Copy the generated configuration or registration command into your client. For the bearer example replace
BEARER_AUTH_TOKENwith the mock credentialdemo-tokenin your local client configuration. This credential belongs only to this local demo. - Restart the client, list tools, then call
ping. The response should containstatus: ok. MCP Inspector provides another way to initialize, list, and call the generated server. A completed tool call is the activation checkpoint.
Reproducible examples
The Petstore example uses the same local mock. It provides read-only responses; its write contracts are for inspection. Upstream demo credentials are simulated for Petstore.
Supported scope
| Feature | Scope and limits |
|---|---|
| Input | OpenAPI 3.x, Swagger 2, and Postman JSON/YAML. Local files up to 5 MB. Internal references are resolved. External references must be bundled; recursive reference edges stay finite and require manual review. |
| Runtime | Generated Node and Python projects are installed and tested in CI. Node 22+; Python 3.11+. Regular and compact tools use the same operations. |
| Schema | Scalar/null unions, nested objects, arrays, common bounds and additional-properties policies. Composition and unsupported keywords receive manual-review warnings. OneOf exclusivity needs review in Node. |
| Upstream auth | Named API keys, bearer tokens and Basic credentials. Operation requirements govern generated requests. OAuth token acquisition is not included. |
| Transport | Stdio for local clients; HTTP and legacy SSE are available. Python HTTP uses /mcp. Remote clients need the correct URL and headers. |
| Client setup | Claude Desktop local JSON, Claude Code registration, Cursor JSON and VS Code JSON are provided. Real client/OS certification is pending; verify a tool call on your chosen combination. Remote Claude Desktop requires separate connector setup. |
| Hosting | Docker files use the selected transport. Provider adapters and one-click cloud deploys are not included. Validate HTTPS, secrets and access before exposure. |
| Testing | Browser inspection and mocks stay local. Send real requests through the generated server or local CLI. Metadata scans are heuristics, not security certification. |
Troubleshooting
Missing dist/src/index.js: run the build. Python import errors: use the .venv interpreter. HTTP 401: check the named upstream credentials and the separate MCP access token. Browser storage failure: download the generated archive or portable project as a backup. Remote connection failure: check your reachable URL, endpoint path, HTTPS and client support.
Report a generated-server problemInclude generator version, runtime, transport and a sanitized error. Review attachments; do not post private specs or credentials.