MCP Integrations - Ownership & Troubleshooting

What is MCP?

MCP (Model Context Protocol) lets Assist connect to external platforms, such as Monday and Google Drive. Once connected, you can use the integration’s available tools to access information or carry out tasks from chat.

Access depends on the integration’s connection settings and your permissions in the external platform.

Activating integrations from chat

Assist can turn on an available, connected integration for the current chat when approvals are enabled.

1. Ask Assist to turn on the integration you want to use.
2. Review and approve the activation request.
3. Assist can then use the integration’s available tools in that chat.

For example:

Turn on the Monday integration and read board 9291179010 to confirm its name. Don’t change anything in Monday.

The integration must already be set up and ready to use. Activating it in chat does not replace signing in or completing the connection setup.

If Assist says the integration is not ready, open Integrations in the chat and check whether you need to connect or sign in to your external account.

Editing a custom integration

You can edit an existing custom integration without removing it and adding it again. You’ll need permission to manage integrations.

1. Open Library and select Integrations.
2. Find your custom integration and click Edit.
3. Update the details you need to change.
4. Click Update Integration.
5. Reopen Edit to confirm your changes saved.
6. Test the integration in chat to check it still works.

This editing feature applies to custom integrations. Pre-built Marketplace connectors are not covered by it.

Ownership & Responsibility

Connection issues can involve Assist, the external platform or your account setup. These responsibilities help identify where to investigate.

Assist Team

• Platform stability
• Integration framework functionality
• Errors within Assist

Third-party platform

For example, Monday or Google Drive:

• Its authentication service
• API availability
• Permissions within its own system

Workspace owner or user

• Selecting the correct external account when signing in
• Checking the required permissions
• Managing access to integrations within Assist

Common issues

You may encounter:

• An internal server error after signing in
• A repeated sign-in or authentication loop
• A permissions error
• A Connect button that fails after authentication
• An existing connection that appears stuck
• An integration marked as not ready
• An integration that connects but does not have the tool needed for your request

What to try first

If an integration is not working:

1. Check that you are signed in to the correct external account.
2. Confirm that account has access to the information or workspace you need.
3. Re-authenticate the integration if prompted.
4. Refresh your browser and try again.
5. If authentication still fails, try connecting in an incognito window.

If the integration is active but cannot complete a request, check which tools are available. A connected integration may still need extra information, such as a board ID, to perform a particular task.

When to contact Assist Support

Contact Assist Support if:

• The issue continues after re-authentication
• You repeatedly receive an internal server error
• A connection cannot be reset or removed
• Multiple users are affected
• The integration fails despite the correct account and permissions

Include the integration’s name, what you were trying to do, the error message and a screenshot where possible. Do not include passwords or API keys.