Skip to main content
This guide covers the MCPJam SAML 2.0 and SCIM 2.0 integration in the Okta Integration Network (OIN). Okta manages user provisioning and organization access; MCPJam manages application roles separately.
The MCPJam catalog submission is under review. The catalog installation steps below apply once the listing is published. If MCPJam is not available in your catalog, contact [email protected] for assisted setup. Do not select a similarly named application or a generic SCIM test app.

Prerequisites

  • An MCPJam organization with enterprise SSO and provisioning enabled.
  • An Okta administrator who can add applications, assign users and configure provisioning.
  • Organization-specific SSO and provisioning setup links from your MCPJam contact. Keep their credentials private.
  • Your users’ email domain verified for your MCPJam organization. Your MCPJam contact helps configure this before the pilot.
  • A pilot user with a work email address in that domain.

Supported features

This guide does not configure importing MCPJam users or profile changes back into Okta, password synchronization, group push, or IdP-controlled application roles. Assigning an Okta group to the application assigns its users; it does not grant those users MCPJam admin access.

Configuration steps

Complete SAML setup and a pilot sign-in before enabling SCIM provisioning.

Before you begin: open your organization’s setup portal

MCPJam uses a separate, organization-specific setup portal for your identity provider configuration. Signing in to the MCPJam application as an organization admin does not itself open this portal.
  1. Contact [email protected] with your MCPJam organization name and the work email address of the Okta administrator who will configure SSO. Request an SSO setup invitation for that organization. Do not send passwords, API tokens or client secrets.
  2. Open the setup invitation sent to that administrator. Check that it is for the intended MCPJam organization, then choose Okta SAML.
  3. Keep the portal open alongside your Okta Admin Console. The portal provides the MCPJam service-provider values used below. Enter your Okta application’s Metadata URL in this portal to connect your Okta organization to MCPJam.
  4. Complete SAML setup and verify a pilot sign-in. Then request the provisioning setup invitation for the same organization to obtain its SCIM endpoint and bearer token.
You do not need a WorkOS dashboard account. Use the setup invitation supplied for your organization; do not reuse another organization’s setup link or credentials. If the invitation is missing or expired, ask MCPJam support for a replacement before continuing.

1. Add MCPJam from the OIN catalog

  1. In the Okta Admin Console, open Applications → Applications.
  2. Select Browse App Catalog, search for MCPJam, and open its listing.
  3. Select Add Integration, enter an application label and continue.
  4. Open the SSO setup link supplied by MCPJam and select Okta SAML.
  5. Copy your complete SP Entity ID into the integration’s SP Entity ID field. The integration constructs the SAML ACS URL from this value.
  6. For SCIM Base URL, use only the directory identifier following /scim/v2.0/ in your provisioning endpoint. Obtain this from your organization-specific provisioning setup link. It is not the bearer token.
  7. Save the integration. Use only the values issued for your organization; identifiers are case-sensitive.

2. Complete SAML configuration

  1. Open the application’s Sign On tab and select SAML 2.0 if prompted.
  2. Use the user’s work email as the application username and SAML Name ID.
  3. Under Attributes (Optional), configure the immutable user identifier: add oktaUserId with value user.getInternalProperty("id").
  4. Ask your MCPJam contact to map this connection’s IdP ID to oktaUserId. Do this before the first test sign-in.
  5. Copy the app’s Metadata URL from Sign On to the MCPJam SSO setup portal and complete the connection setup.
  6. Under Assignments, assign the pilot user. Test the SP-initiated and IdP-initiated flows below before assigning the rest of the team.
The integration supplies the email, given-name and family-name SAML attributes. Do not add role or group assertions expecting them to change MCPJam permissions.

3. Enable SCIM provisioning

  1. Open your MCPJam provisioning setup link and choose Okta. Copy the directory identifier into SCIM Base URL in the app’s general settings if not already configured. The resulting endpoint must match the full SCIM endpoint shown by the setup portal.
  2. In the Okta app, open Provisioning → Integration → Configure API Integration and enable API integration.
  3. Paste the setup portal’s bearer token into API Token. Paste only the token; do not add Bearer, and do not paste the directory identifier.
  4. Select Test API Credentials. Save only after the test succeeds.
  5. Open Provisioning → To App, select Edit, and enable Create Users, Update User Attributes and Deactivate Users. Save.
  6. Keep password synchronization disabled. Users authenticate through SAML.

4. Check profile mappings

Use the following identity fields. Additional business-profile attributes such as department, manager, title, postal address and telephone number are not required by MCPJam. Okta manages the SCIM active state through lifecycle operations. The server returns the SCIM id; do not manually replace it. Preserve identifiers and schema-required attributes maintained by the connector. Keep the username and work email consistent. Contact MCPJam before changing a provisioned user’s email or domain, so account linking and domain management can be checked.

5. Test the user lifecycle

  1. Assign a pilot user under Assignments. Verify successful provisioning in Okta and sign in to the intended MCPJam organization.
  2. Change the pilot user’s given or family name in Okta. Verify the update in the connected directory; the updated name should appear after a fresh login.
  3. Unassign the pilot user from the provisioning app. Verify that they lose access to the MCPJam organization, including from an existing session.
  4. Reassign the user and verify that they can authenticate and access the organization again.
If your assisted setup uses separate SAML and provisioning apps, assign the pilot user to both and unassign from the provisioning app to test offboarding.

SP-initiated SSO

  1. Open MCPJam in a private browser window.
  2. Select Sign in and enter the assigned user’s work email address.
  3. MCPJam routes the verified email domain to your organization’s Okta SSO connection. Complete Okta authentication and any required MFA.
  4. Verify that MCPJam opens with access to the intended organization.
If the same email can access multiple organizations, ask your MCPJam contact for the organization’s sign-in link. A successful login to another organization is not a successful test of this connection.

IdP-initiated SSO

Sign in to your Okta dashboard and select the MCPJam tile. Complete any required authentication and verify access to your MCPJam organization.

Roles and limitations

MCPJam has separate owner, admin, member and guest roles. Organization owners manage role assignments in MCPJam. SCIM provisions and removes organization access, but this integration does not currently synchronize Okta group or role changes into MCPJam admin/member permissions. Deactivation applies to the connected organization. It does not delete the person’s data or memberships in unrelated MCPJam organizations. An explicit removal performed in MCPJam is not automatically undone by an IdP reactivation. OIDC is a separate, optional setup and is not part of this SAML/SCIM catalog configuration. Contact MCPJam before configuring it.

Troubleshooting

Open your organization’s SSO setup invitation, not the MCPJam application settings or the WorkOS dashboard. Select Okta SAML and enter the Metadata URL from your Okta application’s Sign On tab. If you have only an MCPJam sign-in account, contact [email protected] with your organization name and Okta administrator’s work email to request the setup invitation.
Ask [email protected] to send a replacement to your organization’s Okta administrator. Specify whether you need SSO or provisioning setup. Do not include the expired link, passwords or bearer tokens in your support email.
The listing may still be under review. Contact [email protected] for assisted setup; the catalog steps become available after publication.
Compare the full SP Entity ID and ACS URL with your organization’s setup portal. Check for extra spaces, missing characters or values from another organization.
Verify the oktaUserId SAML statement uses user.getInternalProperty("id") and ask your MCPJam contact to verify the IdP ID mapping for the connection.
Confirm the user’s email domain is verified for the intended organization and that the user is assigned to the correct Okta app. Ask MCPJam for an organization-specific sign-in link if needed.
Check the directory identifier and bearer token against the same setup portal. They are different values. Copy the token without a Bearer prefix. A revoked token must be replaced with a valid token for that directory.
Suspending an Okta user does not send the SCIM deactivation used by this integration. Unassign the user from the provisioning app or deactivate the Okta account, then verify the provisioning operation succeeded.
Inactive directory records are retained. Their presence does not grant access; verify that the MCPJam organization membership is inactive and access is denied.
Application roles are managed in MCPJam. Group assignment controls application assignment, not MCPJam admin/member roles.

Support

Email [email protected] with the organization name, failing operation, timestamp and error message. Never include passwords, API tokens or client secrets.