MCP client troubleshooting
MCP client reconnecting in ChatGPT, Claude, or Codex?
Use this five-minute sequence to identify whether the failure is the MCP endpoint, service health, OAuth session, Stackyapper grant, or a separate provider connection.
Short answer: “Reconnecting” usually means the client could not complete or restore its MCP transport or authorization session. Check Stackyapper health and the exact client URL first. Then renew OAuth, verify workspace tool grants, and only then reconnect an individual provider app if its status says it needs attention.
Five-minute MCP reconnect check
| Check | Expected result | If it fails |
|---|---|---|
| Service health | https://mcp.stackyapper.dev/health returns status: ok | Wait before changing client or provider settings. |
| Client URL | ChatGPT uses the root; Claude and Codex use /mcp | Remove the incorrect connection and add the canonical URL below. |
| OAuth | A new sign-in completes and returns to the client | Remove the saved connection, add it again, and finish fresh consent. |
| Tool grants | At least one approved tool appears | Ask a workspace administrator to review app, group, and user grants. |
| Provider status | The required app is connected in Stackyapper | Reconnect only that provider from the Apps page. |
Client connection versus provider connection
These are separate sessions. The MCP client connects to Stackyapper; Stackyapper then uses an approved provider connection such as HaloPSA, NinjaOne, or Hudu. A client can be healthy while one provider needs attention, and a provider can be healthy while a user has no tool grant. Diagnose the layer named by the error before replacing credentials.
ChatGPT keeps reconnecting
- Confirm the custom app URL is
https://mcp.stackyapper.dev, without/mcp. - Open ChatGPT Apps settings, disable or remove the saved Stackyapper app, and add it again.
- Complete the new Stackyapper OAuth flow in the same browser profile.
- Start a new chat and enable Stackyapper before testing an approved read tool.
ChatGPT plan eligibility and administrator controls can change. Use OpenAI’s current developer-mode and MCP guide for the current app interface.
Claude keeps reconnecting
- Confirm the custom connector URL is
https://mcp.stackyapper.dev/mcp. - Open Claude Settings → Connectors and reconnect Stackyapper.
- Complete OAuth, then start a new conversation so Claude reloads the available tools.
- If no tools appear, have an administrator review the user’s Stackyapper grants.
You normally do not need to reset Claude itself. Anthropic’s remote MCP connector guide remains the source of truth for its current connector interface and eligibility.
Codex keeps reconnecting
Confirm the remote server entry in ~/.codex/config.toml:
[mcp_servers.stackyapper]
url = "https://mcp.stackyapper.dev/mcp"- Run
codex mcp listto confirm the server is configured and enabled. - Run
codex mcp login stackyapperand complete OAuth in the browser. - Restart the Codex client. In the terminal UI, use
/mcpto inspect active servers.
These commands and the Streamable HTTP url setting follow the official Codex MCP documentation.
Connected, but no tools appear
Reconnecting the client will not create authorization. In the Stackyapper portal, verify the selected workspace, required app connection, group grants, user exceptions, and tool risk policy. The client only receives the subset that is both available and granted at request time. See the authorization and isolation model for the full sequence.
If reconnecting continues
- Record the client name, UTC time, endpoint, and visible error without copying tokens or authorization codes.
- Confirm whether every client fails or only ChatGPT, Claude, or Codex.
- Confirm whether every tool is missing or only one provider app is unavailable.
- Send those diagnostic details to support; do not publish credentials, cookies, or OAuth callback URLs.
For initial configuration rather than recovery, use the complete MCP client setup guide.
Frequently asked questions
Why does my MCP client keep reconnecting?
Reconnecting usually means the client could not complete or restore its MCP transport or authorization session. Confirm service health and the client-specific URL first, then renew OAuth and check Stackyapper workspace grants.
Why is Stackyapper connected but showing no tools?
A healthy client connection does not grant every app. The signed-in user must have at least one connected app and an applicable workspace, group, or user tool grant.
Do I need to reset Claude to reconnect MCP?
Usually not. Reconnect the custom connector, complete a fresh OAuth sign-in, and start a new conversation. Resetting unrelated Claude application data does not repair a missing workspace grant or disconnected provider app.
Which Stackyapper URL should ChatGPT, Claude, and Codex use?
ChatGPT uses https://mcp.stackyapper.dev. Claude and Codex use the Streamable HTTP endpoint at https://mcp.stackyapper.dev/mcp.
Client interfaces and plan eligibility are controlled by their respective vendors and may change. Follow the linked vendor guides for the current interface.