Client setup
Connect a Generated MCP Server to Claude Desktop
Claude Desktop can launch the generated Node process locally and discover its tools through MCP. This is useful for testing an API wrapper before deciding whether a remotely hosted server is justified.
Generate your MCP serverCompile the server first
The configuration included in the ZIP points to dist/stdio.js, so run the TypeScript build after installing dependencies. Replace the placeholder path with the absolute path on your computer.
npm install npm run build node /absolute/path/dist/stdio.js
Supply environment variables safely
The generated .env.example documents the variables but the stdio process must receive their actual values. Use the client configuration or a secure process launcher, and never commit the credential.
Restart and test discovery
Restart Claude Desktop after changing its MCP configuration. Confirm the server starts, inspect the available tools, and test a predictable read-only request before writes.
Frequently asked questions
Why does nothing appear after editing the config?
The most common causes are an incorrect absolute path, a project that has not been built, missing environment variables, or invalid JSON.
Does Claude Desktop receive my OpenAPI file?
No. It sees the MCP tool schemas exposed by the local generated server.