Connected Apps
Connected apps are third-party applications — AI assistants through the MCP server — that act inside SignStack on a user's behalf through OAuth 2.1. SignStack is the authorization server for its own API: the user signs in, chooses one organization and one namespace, approves a scope set, and the app receives tokens bound to exactly that.
How a connection works
- The app sends the user to
GET /v1/oauth/authorize(authorization-code flow, PKCES256required,staterequired). - SignStack validates the request and shows the user a consent screen where they pick the namespace and see which requested scopes they hold there. Scopes the user does not hold are never granted; a pre-registered client may have some scopes marked optional, and those are granted only if the user opts in.
- The app exchanges the returned
codeatPOST /v1/oauth/tokenfor an access token (a JWT, 1 hour) and a refresh token (opaque, rotating, 90 days of inactivity). - The app calls the API with
Authorization: Bearer <access_token>exactly like an API-key access token. Every endpoint that accepts an access token accepts a connected-app token; the token'saudmust be this API, so a token issued for another SignStack resource is refused. - On refresh the granted scopes are re-intersected with what the user currently holds — a demotion shrinks the app's access within one token lifetime; scopes never grow on refresh. Presenting a rotated-out refresh token revokes the whole connection.
Discovery
GET /.well-known/oauth-authorization-server (RFC 8414) and GET /.well-known/oauth-protected-resource (RFC 9728) describe the server. Clients obtain a client_id in one of three ways: pre-registration by SignStack (verified clients, which may hold privileged scopes), a Client ID Metadata Document (an HTTPS URL used as the client_id, fetched and validated by SignStack — what Claude and Claude Code use), or Dynamic Client Registration at POST /v1/oauth/register (a secret is issued only to a client that asks for one). Self-registered clients are shown as unverified on the consent screen and may request only the self-service scope set workflow:read workflow:create workflow:update resource:read resource:create resource:update scenario:read scenario:create scenario:update shareable-link:read shareable-link:create shareable-link:update.
MCP server
POST /mcp is SignStack's Model Context Protocol endpoint for AI assistants (Claude, Claude Code, ChatGPT, Gemini). It is a separate OAuth resource: request resource=<api>/mcp when authorizing, and the access token carries that audience — it is refused on REST routes, and REST tokens are refused at /mcp. GET /.well-known/oauth-protected-resource/mcp is its metadata. See the guide Connecting AI Assistants (MCP).
Managing connections
Users see and revoke connections in Studio (Settings → Integrations) or through the connected-apps endpoints below. Revoking a connection stops refresh immediately and refuses its access tokens on the next request.
- get/v1/oauth/authorize
- post/v1/oauth/token
- post/v1/oauth/revoke
- get/.well-known/oauth-authorization-server
- get/.well-known/oauth-protected-resource
- get/.well-known/oauth-protected-resource/mcp
- post/v1/oauth/register
- post/mcp
- get/v1/orgs/{orgId}/namespaces/{namespaceKey}/connected-apps
- get/v1/orgs/{orgId}/namespaces/{namespaceKey}/connected-apps/{grantId}
- delete/v1/orgs/{orgId}/namespaces/{namespaceKey}/connected-apps/{grantId}
- get/v1/me/connected-apps
