Cursor supports remote MCP servers natively, so you can point it straight at the endpoint with a url and headers entry in mcp.json, no bridge required. For token detail, see Authentication.
The endpoint is:
https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp
Replace YOUR_ACCOUNT_ID with your account subdomain or numeric id (the value in your dashboard URL).
Native remote (recommended)
Edit ~/.cursor/mcp.json (or per-workspace .cursor/mcp.json) and add:
We recommend keeping the token out of the config file by referencing an environment variable (INTEGRATEIO_MCP_TOKEN above) rather than pasting the raw token. Set the variable in your shell profile to a Personal Access Token (see Authentication). If you prefer, you can paste the literal Bearer YOUR_ACCESS_TOKEN value directly instead.
Fallback: mcp-remote bridge
On an older Cursor build without native remote MCP support, use the mcp-remote bridge instead: set "command": "npx" with args ["-y", "mcp-remote", "https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp", "--header", "Authorization: Bearer YOUR_ACCESS_TOKEN"]. See Other clients for the full bridge form.
Verify
Restart Cursor, open the MCP settings, and confirm integrateio shows its tools. Trouble connecting? See Troubleshooting. Last modified on October 27, 2026
