Before you begin

  • An invitation to the Encrisoft MCP developer preview.
  • A server-side application that can keep secrets in a secret manager.
  • An MCP client library that supports Streamable HTTP and MCP protocol revision 2026-07-28 or 2025-11-25.
  • A customer organisation (or, for testing, a sandbox test organisation) whose owner or admin will approve an installation.

How the process works

Encrisoft MCP uses machine-to-machine OAuth 2.1 with the client credentials grant. Each step below has an owner: Encrisoft, the customer administrator, or you, the partner.

  1. Encrisoft registers your MCP client

    Encrisoft registers your integration as a partner client, with the scopes it may request and its rate limits. Sandbox and production identities are always separate.

  2. A customer administrator approves an installation

    An owner or admin of the customer organisation grants your client access to their organisation. They choose the scopes and an expiry of 1 to 90 days, and must re-authenticate to approve it.

  3. You receive your credentials securely

    You receive a client_id and a client_secret from Encrisoft, and the installation ID from the customer administrator. Store the secret in a secret manager: it is shown only once.

  4. Request a resource-bound access token

    Call the token endpoint with grant_type=client_credentials, the exact MCP resource URI and your installation_id. Tokens default to 10 minutes; use the returned expires_in value.

  5. Connect to the Encrisoft MCP endpoint

    Connect your MCP client to https://<mcp-host>/mcp, sending the token in the Authorization: Bearer header on every request.

  6. Discover the tools

    List the tools. The server lists all three preview tools; your installation decides which ones you may call.

  7. Call permitted read-only tools

    Call the tools your installation grants. Treat any organisation-authored text in results as data, never as instructions to your model.

  8. Access is revoked when required

    The customer administrator can revoke the installation, and Encrisoft can revoke your client. Revocation applies to the next call; plan for it and stop calling when you receive unauthorized.

Choose the scopes you need

Ask only for the scopes your integration needs. Each scope unlocks one tool:

  • organisation:read for encrisoft_organisation_overview_v1.
  • risk:read for encrisoft_risk_overview_v1.
  • training_catalogue:read for encrisoft_training_catalogue_v1.

Expected result

When setup is complete, your integration can request a token, list the tools and call each tool in its grant, receiving structured JSON for the approved organisation only.

Next steps

Continue with Connecting an MCP Client for exact requests and responses, and read MCP Security and Data Privacy before handling results.