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, but they do not offer the same tools. The hosted server has 80 tools and is the supported way to connect. The local npm package is older, has its own 28 tools, and needs an API key, which is not self-serve.

Cloud endpoint

Point any HTTP-capable MCP client at that URL, then sign in to SmartAlex in your browser and press Allow. See Authentication.

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

A signed-in AI app acts as you, in the workspace you last opened in SmartAlex, with your role’s permissions. The gateway scopes every read and write to that workspace, so one sign-in can never reach another tenant’s data. Security and permissions covers what a connected app can do and how to disconnect it.

Authentication

How sign-in works, and rate limits.

Getting started

Connect a client in two minutes.