Connecting
Connect a compatible AI agent or client to your Stackless MCP server.
Connect an AI agent or client
-
Open your AI agent or client's connector settings and choose the option to add a custom MCP server or connector.
-
Enter a name such as Stackless and your workspace MCP endpoint:
https://your-workspace.stacklessdata.com/api/v1/mcp/transportFor ChatGPT, use
/api/v1/mcp/openai/transportinstead. -
Replace
your-workspacewith the hostname supplied by your Stackless administrator, then start the connection. -
Your client opens Stackless in a browser. Sign in with your normal Stackless account. The consent page, Connect <client> to Stackless, asks you to let the client Use Stackless MCP tools as you. Only continue if you trust the client, then click Authorize.
-
Return to your client and confirm that Stackless appears as connected.
Stackless uses OAuth with PKCE and registers the client automatically, so there is no client ID or secret to copy. Your client refreshes its access in the background; you are asked to authorize again only if the connection is revoked or unused for a long time.
Your Stackless administrator may instead make the connector available through your organization's connector directory. In that case, select Stackless from the directory and complete the same browser authorization.
Never put an access token, session cookie, or other secret in the connector URL.
Terminal agents (beta)
Claude Code, Codex, and other terminal agents can run the stackless-mcp
package locally instead of using the hosted endpoint. Ask your Stackless contact
for the current package version, install uv, then:
-
Sign in once:
uvx stackless-mcp==<version> login --base-url https://your-workspace.stacklessdata.comThis opens the Stackless sign-in in your browser and stores a session for up to 30 days in your operating system's keyring.
-
Add the server to your agent. For Claude Code, in
.mcp.json:{ "mcpServers": { "stackless": { "command": "uvx", "args": [ "stackless-mcp==<version>", "--base-url", "https://your-workspace.stacklessdata.com" ] } } }For Codex, add the same command and arguments under
[mcp_servers.stackless]in~/.codex/config.toml. -
Check the setup with
uvx stackless-mcp==<version> doctor --base-url https://your-workspace.stacklessdata.com.
Use --toolsets to load only some tool groups, for example
--toolsets catalog,dashboards, and logout to remove the stored session.
Disconnect or change accounts
Remove Stackless from the agent or client's connector settings to disconnect it. To revoke access on the Stackless side, sign out of Stackless in your browser: signing out revokes all of your MCP sessions. Administrators revoke a user's sessions by removing their roles or deleting the user. Reconnect afterward to authorize the correct account.