makeplane / makeplane/plane

Unable to establish Plane MCP Integration with Supergrok/xAI Connectors

Open
#9,055 1 comment 0 reactions 1 assignee View on GitHub

@Saurabhkmr98 is already working on this.

Since May 14, 2026.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Summary of troubleshooting shown below, generated from chat with my Grok instance.

Sequence of Events
  1. 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.

  2. 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.
Image Image
  1. 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.
  2. 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.