Client setup
Connect a Generated MCP Server to Cursor
Cursor can start a local MCP server as a child process and communicate with it over stdio. The generated ZIP includes a configuration example with a placeholder absolute path.
Generate your MCP serverBuild the generated project
Unzip the project, install dependencies, copy the environment template, set the upstream base URL and credential, then compile TypeScript.
npm install cp .env.example .env npm run build
Configure the stdio command
Point Cursor to Node and the absolute path of dist/stdio.js. Add required environment values through your normal secret-management workflow rather than committing them to the repository.
Verify tools before real writes
Inspect the advertised tool list and call read-only endpoints first. Review generated descriptions, required fields, and the selected base URL before enabling create, update, or delete operations.
Frequently asked questions
Why does the path need to be absolute?
The MCP client may start the process from a different working directory, so a relative path is unreliable.
Can Cursor use the HTTP entry point?
Cursor versions with remote MCP support may use HTTP, but stdio remains the simplest local setup for the generated project.