Cursor connects directly to the hosted ApexGenius streamable HTTP server. No local wrapper is required.
Choose the configuration scope
- Use
~/.cursor/mcp.json to make ApexGenius available to your Cursor user across projects.
- Use
.cursor/mcp.json in a project to share the server declaration with that project.
Project configuration takes priority when the same server name exists in both locations.
Add the server
Create or update the chosen mcp.json file:
Save the file, open Cursor’s MCP settings, and find ApexGenius. Complete the browser authorization when Cursor requests it, then confirm the server is enabled and its tools are available.
The top-level key is mcpServers. Do not copy the VS Code servers shape into Cursor. Do not add account credentials or a hand-written authorization header to this file.
Verify the connection
Open an Agent conversation with ApexGenius available and ask:
Confirm the response uses the intended Salesforce project and production org or sandbox. If Cursor shows an authorization or connection error, reopen MCP settings and retry the browser sign-in before changing the endpoint.
Sharing project configuration
The project file can be committed so teammates receive the same server declaration. Each teammate should complete their own ApexGenius authorization. Review any MCP configuration before trusting and enabling it in a repository.
For current file locations, remote server syntax, and transport support, see Cursor’s MCP documentation. 
