Connection troubleshooting
minddy MCP connects an external assistant to minddy; personal MCP connections let Numo call another server.
Locate the failed connection
minddy MCP connects an external assistant to minddy; personal MCP connections let Numo call another server. They have different account tabs and credentials. For personal MCP, inspect the connection status in account settings and use its test/reconnect action. OAuth discovery, dynamic registration, PKCE and refresh are supported, but a catalog entry does not bypass provider approval, developer preview or registered-app requirements. Confirm current provider requirements before assuming a minddy defect.
Reconnect without losing the access boundary
Register the exact displayed callback in the provider OAuth app when existing client credentials are required. Desktop OAuth opens in the system browser and returns to the app. Personal MCP connections used by Numo require public HTTPS; local commands and private network servers are unsupported. For an external assistant connecting to minddy MCP, see network access for your instance. Put bearer tokens and custom secrets in authentication/headers, not query URLs. Changing the URL clears saved credentials and headers. Disabling/removing stops new calls, but a request already sent may finish. Routine connections belong to the current project owner; ownership changes cannot reuse the previous owner’s personal access.
Inspect the outcome before repeating a call
Calls from Numo to personal MCP servers have a 30-second deadline, 1 MiB transport limit and 64 KB result limit. A timeout does not prove a remote mutation failed. Check the destination before retrying. For API 401, verify key kind/instance and revocation without logging the key; wrong kind returns 403. For webhooks, inspect last status, public destination reachability, raw-body HMAC verification and delivery_id deduplication. Best-effort dropped deliveries have no durable retry queue. Preserve controlled codes and times, removing private content and credentials.
Check provider permissions and synchronization
Git adapters target github.com and gitlab.com. Confirm the linked repository, installation access and selected connection channel. GitHub issue synchronization needs Issues read/write and Issues, Issue comments and Issue dependencies webhook subscriptions; existing installations must accept changed permissions. Older payload timestamps cannot overwrite newer local edits. Duplicate deliveries use remote identities to avoid repeats. Inline attachment URLs remain forge links rather than copied file bytes. Verify remote and local state before reconnecting or retrying a write and share only redacted diagnostics.