Troubleshoot MCP

Fix Mogplex MCP installation, OAuth, tool discovery, authorization, and automation request errors.

Start by confirming that the client is configured with this exact endpoint:

https://www.mogplex.com/api/v1/mogplex/mcp

Common symptoms

SymptomWhat to check
Browser login succeeds but tools are missingRestart the agent session so it reloads the server catalog through tools/list.
The client repeatedly requests authenticationConfirm both the server URL and explicit OAuth resource use the exact www.mogplex.com endpoint above.
401 UnauthorizedRe-run client login. The token may be expired, revoked, issued to an unapproved client, or minted for the wrong resource.
403 Forbidden with a PATReissue the PAT with write when the requested tool mutates state.
Automation update returns BAD_REQUESTSend a complete graph with nodes, edges, and an optional valid viewport.
Installation id returns BAD_REQUESTUse a positive safe integer returned by mogplex_list_repos.
An automation does not run the latest draftPublish the draft before triggering it. Triggers use the active published version.
A model change is rejectedUse a model id currently returned by mogplex_list_models.

Re-authenticate a client

Codex

codex mcp login mogplex
codex mcp get mogplex

Claude Code

Start Claude Code, run /mcp, select mogplex, and authenticate again.

OpenCode

opencode mcp auth mogplex

For Cursor, open MCP settings, confirm the Mogplex server is enabled, and start authentication again from the server controls.

Verify PAT access directly

When debugging a PAT-only client, initialize the endpoint directly:

curl -sS \
  -X POST \
  -H "Authorization: Bearer $MOGPLEX_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}' \
  https://www.mogplex.com/api/v1/mogplex/mcp

Do not paste the token or command output into a public issue. The Mogplex MCP endpoint reference documents the expected initialize response and JSON-RPC errors.

Next checks

  • Revisit Install for the canonical client command.
  • Review Security for audience and scope rules.
  • Review Tools for tool names and arguments.
  • Use Support if the client still cannot connect after a fresh login.
Edit on GitHub

On this page