Summary of troubleshooting shown below, generated from chat with my Grok instance.
Sequence of Events
-
Initial Recommendation: User requested setup instructions for Plane MCP alongside existing connectors in Grok. I provided the standard OAuth flow using https://mcp.plane.so/http/mcp via grok.com/connectors → Custom Connector.
-
First Attempt (OAuth):
- The Plane OAuth consent screen loaded successfully (GitHub SSO session active).
- You selected the “” workspace and approved read/write permissions.
- Grok’s Custom Connector popup displayed “Complete authentication in the popup window...” and remained stuck in a hung “Connecting...” state indefinitely.
-
Troubleshooting Steps Applied:
- Recommended deleting the partial connector, clearing browser cache/cookies, using Incognito mode, and full logout/re-login (including GitHub SSO on Plane).
- Suggested switching to the PAT (Personal Access Token) method to bypass browser OAuth.
-
Second Attempt (PAT):
- Used the dedicated endpoint
https://mcp.plane.so/http/api-key/mcp.
- Grok again showed the same hung authentication window.
- No prompt appeared for entering the API key or headers (Authorization: Bearer ... and X-Workspace-Slug).
- Behavior identical to the OAuth attempt.
Key Observations
- The Plane OAuth consent screen functions correctly.
- The hang consistently occurs on the Grok side during the post-OAuth or PAT handshake phase.
- GitHub SSO on your Plane account may contribute to redirect/cookie conflicts.
- No error message is displayed beyond the indefinite loading state.
- Other MCP connectors in your Grok account function normally, isolating the issue to Plane integration.
Reference Links for Similar / Related Issues
Summary of troubleshooting shown below, generated from chat with my Grok instance.
Sequence of Events
Initial Recommendation: User requested setup instructions for Plane MCP alongside existing connectors in Grok. I provided the standard OAuth flow using
https://mcp.plane.so/http/mcpvia grok.com/connectors → Custom Connector.First Attempt (OAuth):
Troubleshooting Steps Applied:
Second Attempt (PAT):
https://mcp.plane.so/http/api-key/mcp.Key Observations
Reference Links for Similar / Related Issues