MCP Integrations - Ownership & Troubleshooting

What is MCP?

MCP (Model Context Protocol) integrations allow Assist 2.0 to securely connect to external platforms (e.g. Monday, Google Drive, etc.) so users can pull in data, trigger actions, or connect workflows directly from chat.

Each integration requires authentication and appropriate workspace permissions.

Ownership & Responsibility

To ensure clarity, ownership is divided as follows:

Assist 2.0 Team

Platform stability
Integration framework functionality
Server-side errors within Assist 2.0

Third-Party Platform (e.g. Monday)

Authentication flow
API availability
Permission structure within their system

Workspace Owner / User

Selecting the correct account during authentication
Ensuring correct workspace permissions
Managing who has access to connected tools within the workspace

Common Issues

Users may encounter:

Internal server error after authentication
Authentication loop
Permissions error
"Connect" button fails after successful auth
Existing connection appears stuck

What You Can Try

Before raising to Tech, please try:

Re-authenticate the integration
Ensure you are logged into the correct external account
Confirm you have the required workspace permissions
Refresh the browser and retry
Try reconnecting in an incognito window

When To Raise to Tech

Please escalate to the Assist 2.0 Team if:

The issue persists after re-authentication
You receive a consistent internal server error
A connection cannot be reset or removed
Multiple users are affected
The integration fails despite correct permissions