Skip to main content
Mintive is the new name for MintMCP.Read the announcement

Set up the Conclude MCP server

The Conclude MCP server lets AI agents manage Conclude, which syncs Slack and Microsoft Teams channels, so an agent can look up your workspaces and channels and connect, change, or disconnect them. This guide covers issuing a Conclude API key, choosing who the key acts as, and installing Conclude from the Mintive catalog.

Prerequisites​

  • A Mintive admin account
  • A Conclude organization on a trial, Pro, or Enterprise plan that is in the Conclude API beta program. Contact Conclude to join the beta, because the API keys page only appears for beta organizations
  • A Conclude admin account to issue the key
  • The Connect channels permission for the person the key acts as, set under Admin console > Account > Roles & permissions. A key that acts as Conclude holds this permission through its scopes instead
  • Conclude added to any private or shared channel that agents should connect, and in Microsoft Teams, the Conclude app installed in the team

Choose who the key acts as​

Every Conclude API key acts as someone, and Conclude checks each request against that identity's access:

Key typeActs asUse when
Acts as youThe Conclude admin who issued the key. The key never reaches more than that admin canOne admin runs channel connections through agents
Acts as ConcludeConclude itself, for a named person (the subject). The key reaches only channels Conclude is in, and its scopes stand in for the subject's permissionsAgents should only reach channels Conclude is in, or the key should stay when the admin who issued it leaves

Only people who have the role from Conclude can issue a key that acts as Conclude. Contact Conclude to get the role.

Issue a Conclude API key​

  1. Go to Admin console > Account > API keys in Conclude.

  2. Click Issue new key.

  3. Enter a Name that says where the key is used (for example, Mintive).

  4. Choose when the key expires. A key lasts at most ten years.

  5. Select Choose what the key can do and pick these scopes:

    ScopeWhat it covers
    org:readYour organization, its workspaces, and its channels
    connections:readwriteReading and changing connections between channels
  6. Choose who the key acts as: Acts as you or Acts as Conclude. The choice only appears if Conclude has given you the role for keys that act as Conclude.

  7. Copy the Client ID, which starts with J-, and the Client secret. Conclude shows the secret only once.

Add Conclude to Mintive​

  1. In Mintive, go to MCP store and open the Catalog tab.
  2. Select Conclude and click Add.
  3. For the authentication method, choose API key that acts as you.
  4. Paste the Client ID and Client secret from the key you issued.
  5. Click Save.

Every agent call through this connector runs as the admin who issued the key, so it reaches the same channels and connections that admin can.

Security considerations​

  • Store the client secret only in Mintive. Conclude keeps just a hash of it, so a lost secret means issuing a new key.
  • Conclude exchanges the key for access tokens that last one hour, and every request is checked against the access of the person the key acts as.
  • A key that acts as you depends on your Conclude account. If you lose a role, the key loses it too, and Conclude revokes the key once you have no active account left in any of your workspaces.
  • A key that acts as Conclude belongs to the organization and stays when the person who issued it leaves. Conclude notifies every admin of your organization when one is issued.
  • With a key that acts as Conclude, Conclude can't confirm that the subject asked for a change, so anyone who can reach the connector acts for the subject. Use gateway access policies to limit who can use it.
  • Conclude's audit log records the key with each change it makes, and the Mintive audit log records which user made each tool call.
  • To revoke access, revoke the key under Admin console > Account > API keys. Its tokens stop working right away.

Troubleshooting​

  • invalid_client: the client ID or secret is wrong, the key is revoked or expired, or the admin a key acts as no longer has an active account. Issue a new key and update the connector.
  • invalid_request with a subject: the subject is not an active user in your Conclude organization. Check the Slack member ID or Entra object ID.
  • unauthorized_client: a subject was entered for a key that acts as you. Remove the subject, or issue a key that acts as Conclude.
  • forbidden: the person the key acts as doesn't have the Connect channels permission.
  • conclude_not_in_channel: Conclude isn't in a private or shared channel, or the Conclude app isn't installed in the Microsoft Teams team. Add Conclude and try again.
  • subject_required: a key that acts as Conclude tried to change a connection without a subject. Add a subject to the connector.

Next steps​