Overview

Encrisoft MCP uses OAuth 2.1 for machine-to-machine access. Partner clients are confidential clients registered by Encrisoft. A client can only obtain a token for an installation: an organisation-specific grant approved by that organisation’s owner or admin.

Client credentials

  • Encrisoft registers partner clients. There is no self-service registration or dynamic client registration.
  • Client IDs start with mcpc_. The client secret is shown once at registration; Encrisoft stores only a hash of it.
  • Clients authenticate to the token endpoint with HTTP Basic (client_secret_basic).
  • Sandbox and production clients are always separate identities.

Installations

  • An installation grants one client access to one organisation.
  • Only an organisation owner or admin with the integrations.manage permission can create one, and approving it requires a fresh step-up re-authentication.
  • Its scopes must be a subset of the scopes Encrisoft allowed for the client.
  • It expires after 1 to 90 days, chosen when it is created.
  • A client can have only one active installation per organisation.
  • It can be revoked at any time. Revocation is immediate for new tokens and applies to the next tool call.

Access tokens

  • Tokens are signed JWT access tokens (typ: at+jwt, RS256).
  • The token audience is the MCP server’s canonical URI, set from the mandatory resource parameter (RFC 8707).
  • Tokens default to 10 minutes and never outlive the installation. Use the returned expires_in value. There are no refresh tokens.
  • Send tokens only in the Authorization: Bearer header.
  • MCP tokens cannot be used with other Encrisoft APIs: they have a different issuer, audience and token type from Encrisoft application sessions.

Scopes and permissions

Each tool needs a scope in the token and in the installation. The administrator who approved the installation must also still hold the matching permission:

  • encrisoft_organisation_overview_v1: scope organisation:read; administrator permission people.read.
  • encrisoft_risk_overview_v1: scope risk:read; administrator permission risk.read.
  • encrisoft_training_catalogue_v1: scope training_catalogue:read; administrator permission courses.read.

Checks on every call

Authorisation is not cached. On every tool call Encrisoft confirms that:

  • the partner client is still active;
  • the installation is neither revoked nor expired;
  • the organisation is active;
  • the tool’s scope is in the token, the installation and the client’s allowed scopes;
  • the approving administrator is still an active owner or admin with the tool’s permission;
  • the client is within its rate limits.

Behind the MCP server, your token is exchanged for a separate internal token that lasts at most 2 minutes. Your token is never forwarded to other Encrisoft services.

Not supported in the preview

  • Interactive user OAuth (authorisation code with PKCE) and consent screens.
  • Dynamic client registration and client ID metadata documents.
  • Refresh tokens.