Skip to main content
Every connector in your project has a built-in flow for generating MCP connection configs. Once an account is linked, you can get a ready-to-paste config for Claude Desktop, Claude Code, Cursor, VS Code, or any other MCP-compatible client in three clicks.

​
Prerequisites

​
How to get your MCP config

1

Open a connector

Go to Connectors in the left nav, then click any connector to open its detail page.
Connectors list showing available connectors with Actions, Configs, and Accounts counts
2

Click 'Use Connector'

Click the Use Connector button in the top-right of the connector detail page. This opens the “Get Started with Connector” panel.
Connector detail page showing the Use Connector button in the top-right header
If the connector isn’t configured yet, you’ll see a setup wizard instead. Complete both steps — create an auth configuration, then link an account — and the Use tab with the MCP tile will appear.
3

Select your account

On the Use tab, click MCP Server under “Use with Agent Client” to expand the tile.Select a linked account from the dropdown. StackOne generates a token for that account automatically.
MCP Server tile showing account selector dropdown
4

Choose your client

Pick the client you want to connect. Supported options:
ClientConfig format
HTTPS MCPDirect URL
Claude DesktopJSON (mcpServers block)
Claude CodeCLI command (claude mcp add)
CursorURL + one-click deep link
VS CodeURL + one-click deep link
Codex CLICLI command
Gemini CLIJSON (mcpServers block)
WindsurfJSON (mcpServers block)
ZedJSON (context_servers block)
KiroJSON (mcpServers block)
RaycastURL
LM StudioURL
Client selection grid showing icons for all supported MCP clients
5

Copy the config

The panel shows the config in the right format for your client, with a copy button.For clients that use a config file (Claude Desktop, Gemini CLI, etc.), the panel also shows the exact file path to paste it into.For Cursor and VS Code, you can skip the copy step entirely and click Add to Cursor or Add to VS Code to install it directly via deep link.
Config panel showing JSON configuration with copy button and file path
Paste the config into the specified file or terminal, then restart your client.

​
What the MCP URL looks like

The generated URL follows this format: 
https://api.stackone.com/mcp?token=<session_token>
The token encodes the account identity and expires after one year. You can regenerate it at any time using the refresh button in the MCP tile.
The token-based URL is useful for quick setup and testing. For production deployments, use your API key and account ID directly. See Authentication & Security for details.

​
Next steps

MCP Quickstart

Full endpoint reference and authentication options

Authentication & Security

Token types, expiry, and production auth patterns