Cursor is an AI code editor with native MCP support. It connects to remote Streamable HTTP servers directly, runs the OAuth flow itself, and needs no wrapper package.
You can also manually edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project) files as above.
The StackOne MCP Server appears with an Authenticate link.
2
Approve the browser prompt
Click Authenticate. Cursor opens StackOne in your browser so you can sign in.Sign in, pick the project and the linked accounts the connector should reach, then Authorize.
Walk through the consent screen
Sign in to StackOne. If you are already signed in to the dashboard you skip straight to the next step.
Check where the connection returns. The line under the client’s logo shows where it goes after you approve. If it names localhost or an app on this device, only continue if you started the connection from that client.
Select a project. Select the project you would like to associate the connection with.
Select accounts and actions. Existing linked accounts are shown. New accounts can be linked by clicking + Link Account. You can either select the whole account (all actions will be granted) or refine by toggling individual actions.
(Optional) Load tools when needed. On by default, and the toggle that puts the connection into Advanced Tool Search. Leave it on for large action sets. Turn it off to hand the agent every selected action up front.
Authorize. Completes the connection; you can return to your client.
Select a project
Select accounts
Toggle actions
If you see a sentence where the Load tools when needed toggle should be, an admin has already settled it for the whole project. See project settings.
3
Verify
Open Customize → MCPs and confirm StackOne shows a green dot, then ask the agent:
What StackOne tools are available?
To change which accounts or actions Cursor can reach, re-run the flow. To revoke it, use Connected Apps in the StackOne dashboard.
Connecting with a session token instead
A session token URL carries its own credential, so it covers the cases OAuth can’t: a shared server, a scheduled job, or anywhere nobody is present to approve a consent screen. For a comparison of each connection method, see Choosing a connection method.From the StackOne dashboard, go to Connectors, open a connector, then click Use in Agent.
Pick a linked account.
Set the expiry (one year by default).
Select HTTPS MCP and copy the URL. It should be in the format of:
This URL covers one linked account, and anyone holding it has that access until it expires, so treat it like a password.To enable Advanced Tool Search, add the tool-mode query parameter to the URL: