Connecting Your AI Assistant
Every client connects to the same hosted endpoint and signs in with your existing ScopeStack credentials:
You don’t create API keys or paste tokens. The first time a client connects, it opens a browser window where you log in to ScopeStack and approve access. After that, the client reconnects on its own.
How Sign-In Works
ScopeStack uses standard OAuth. When your client connects to the URL above, it discovers ScopeStack’s authorization server, opens the login page in your browser, and receives a token tied to your user. The token carries read and write access, so the assistant inherits exactly your role’s permissions — nothing more.
Claude Code (CLI)
Run:
claude mcp add --transport http scopestack https://api.scopestack.io/mcpThe first time you use a ScopeStack tool, a browser window opens for login. Confirm the server is registered with claude mcp list.
Claude (Desktop and Web)
- Open Settings, then Connectors (Integrations on some plans).
- Choose Add custom connector / Add remote MCP server.
- Name it
ScopeStackand enter the URLhttps://api.scopestack.io/mcp. - Save, click Connect, and log in to ScopeStack in the browser window that opens.
ChatGPT
- In a workspace where custom connectors are enabled, open Settings, then Connectors.
- Add a custom connector / MCP server.
- Enter the URL
https://api.scopestack.io/mcpand save. - Authenticate with ScopeStack when prompted.
Remote MCP connectors require a plan or workspace where custom connectors are available.
Cursor
- Open Settings, then MCP (or edit
~/.cursor/mcp.json). - Add a server pointing at
https://api.scopestack.io/mcpover HTTP transport. - Reload, then authenticate in the browser the first time Cursor calls a ScopeStack tool.
GitHub Copilot (VS Code)
- Open the MCP server configuration (Command Palette, then MCP: Add Server, or edit the workspace
mcp.json). - Add an HTTP server pointing at
https://api.scopestack.io/mcp. - Start the server and sign in to ScopeStack in the browser.
Microsoft Copilot Studio
ScopeStack publishes its OAuth authorization and registration endpoints at the discovery paths Copilot Studio checks. Point your agent at the hosted MCP server, https://api.scopestack.io/mcp, sign in to ScopeStack when prompted, then run scopestack_whoami to check the connection.
Verifying the Connection
Ask the assistant to run scopestack_whoami. It is read-only, needs no inputs, and returns the ScopeStack account and user the connection is signed in as. If it answers with your account, you’re connected. You can also ask it to call scopestack_tool_guidance, which returns the recommended workflow for building a project.
Troubleshooting
- HTTP 401 when connecting: Check that sign-in completed. If the token expired or was revoked, reconnect in your client to sign in again.
- A specific tool returns “Unauthorized” or a role error: Check the requested action and your assigned role in ScopeStack. Ask your admin for the required permission. See How the MCP Works.
- HTTP 429 or a rate-limit message: The limit applies to each access token. Wait the number of seconds in
Retry-Afterbefore trying again. - A tool isn’t found: make sure the client finished connecting to the server, then reconnect if needed.
New to ScopeStack?
ScopeStack automates scoping, pricing, and SOW generation for IT services teams. See how it fits your process.