VS Code connects to MCP servers through GitHub Copilot’s agent mode. It supports remote Streamable HTTP servers directly and runs the OAuth flow itself.
VS Code opens StackOne in your browser once the server is added.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.
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) Search & Execute mode. We recommend turning it on for large action sets. See Search & Execute.
Authorize. Completes the connection; you can return to your client.
Select a project
Select accounts
Toggle actions
If you don’t see Search & Execute, it may be disabled for your project. See project settings.
3
Verify
Open Copilot Chat in Agent mode, click the tools icon to confirm StackOne’s tools are listed, then ask:
What StackOne tools are available?
Copilot needs Agent mode to call tools at all. To change which accounts or actions it 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.Generate one from Connectors, open a connector, then Use in Agent. Pick a linked account, set the expiry (one year by default), and copy the URL:
One URL covers one linked account, and anyone holding it has that access until it expires, so treat it like a password. See Choosing a connection method for the comparison with OAuth.There is no consent screen to set Search & Execute on, so add the tool-mode query parameter instead:
