What to hand out
The same URL for everyone in your organization:What the user sees
Authorization happens in the StackOne dashboard, against the user’s own login. A user only ever sees the organizations, projects, and linked accounts they already have access to.1
Sign in to StackOne
The client opens StackOne’s authorization server in a browser. Users who are already signed in to the dashboard skip straight to the next step; everyone else signs in as normal, including SSO.
2
Select a project
A project scopes which accounts the client can be given. Picking one here decides what appears on the next step.
3
Select accounts
Each row is one linked account. Selecting an account grants the client every action enabled on that account’s connector profile.
4
Narrow down the actions
To grant a subset instead, expand an account to list its actions with descriptions and categories, then turn off anything the client should not have. The count in the account header tracks the selection, and the footer totals what is about to be granted.The same screen carries a Search & Execute mode toggle, which swaps the full tool list for a single search tool and execute tool. It is worth turning on for a large action set. See Search & Execute.
5
Authorize
Authorize issues the access token and returns the user to their client. The granted accounts and actions become that client’s tool list.
Who can grant access
Users are typically provisioned as Members, which is what the flow is built around: a Member sees the accounts they linked themselves, plus any they have been added to. That is what makes one URL safe to publish across an organization. Access can also be granted on a single linked account, which is how a shared account (a service mailbox, a company CRM login) reaches someone who is otherwise only a Member. Each person added to an account gets one of two levels:Search & Execute
Granting a large action set produces a large tool list, which costs context on every turn. The Search & Execute mode toggle on the consent screen swaps one-tool-per-action for a search tool and an execute tool. See Search & Execute and Tool Discovery for the trade-off. Admins can settle this for the whole project instead of leaving it to whoever authorizes, under Project Settings → MCP Settings. It applies project-wide to new connections:Clients
Every client takes the samehttps://mcp.stackone.com/mcp.
ChatGPT
Claude Code
Claude Desktop & Web
Codex (OpenAI)
Cursor
Gemini CLI
Goose
n8n
VS Code (Copilot)
Other clients
Clients that need a client ID and secret
Most clients register themselves with StackOne automatically, which is why the URL is usually the whole configuration. A few sign in from a fixed, hosted callback address instead and cannot self-register. Those need a client created in the dashboard first, and you paste its credentials into the client.1
Create the client
Go to Project Settings → MCP OAuth Clients → Create. Give it a descriptive name and one redirect URI per line. This is the callback address the client returns to after sign-in, which the client’s own documentation states.The Common integrations picker fills the redirect URI in for the clients we have confirmed:
Redirect URIs must be
https or a loopback address.2
Copy the credentials
Generate returns the client ID and secret. The secret is shown only once, so store it before you close the panel. If it is lost, create a new client rather than trying to recover it.
3
Configure the client
Paste the credentials into the client along with the endpoints shown beside them:
Then run the flow. The consent screen is the same one every other client shows, and Who can grant access applies unchanged.
Access tokens last one hour and are renewed automatically using the
offline_access refresh token. The grant itself lasts 90 days, after which the user runs the flow again. Revoking under Connected Apps ends it immediately.Don’t see your client?
Any MCP client that speaks the Streamable HTTP transport and supports OAuth can connect. Point it athttps://mcp.stackone.com/mcp and let it run the flow. If a client cannot open a browser for someone to approve the prompt, use a session token URL instead.
Reviewing and revoking access
Every authorization is a grant against the user who approved it, not against a project API key. Users manage their own grants under Connected Apps in the dashboard, where revoking one immediately stops that client’s tool calls. Revoking access does not unlink the account or change the connector profile. The account keeps working for every other client.Session token URLs
Connecting with a session token instead
Connecting with a session token instead
Token URLs came before the OAuth flow and are still supported. They cover the cases OAuth cannot: a shared server, a scheduled job, or anywhere nobody is present to approve a prompt.The access is built into the URL itself, which is the trade-off: one leaked link exposes the account it was minted for.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.
For calling MCP from your own systems with an API key, see MCP in the Embed tab.
Optimize and secure
With your agent connected, use StackOne’s platform features to optimize performance and secure every call.Search & Execute
Reduce context and save tokens.
Defender
Block prompt injections before they reach your agent.