Skip to main content
There are two ways to run the SmartAlex MCP server, and they connect to the same place: a tenant-scoped API gateway that fronts your workspace.

​
Local vs cloud

Both paths end at the same tenant-scoped gateway, so the tools, resources, and prompts you get are identical. The only difference is where the server process runs and how you authenticate.

​
Cloud endpoint

Point any HTTP-capable MCP client at that URL and authenticate with OAuth or an API key.

​
Stateless by design

The cloud server runs stateless: each request spins up a fresh server instance, handles the call, and tears down. There’s no long-lived session to keep alive. For you this means one thing: if a client shows a reconnection notice, just reconnect, every request is independent, so nothing is lost.

​
Workspace isolation

Every credential resolves to exactly one workspace. An API key belongs to the workspace it was created in; an OAuth token resolves to the user’s active workspace. The gateway scopes every read and write to that workspace, so one credential can never reach another tenant’s data.

Authentication

API keys, OAuth, scopes, and rate limits.

Getting started

Connect a client in two minutes.