Troubleshooting

The client has no Simplified tools

Confirm that the hosted URL is correct, the server is enabled, and authentication has completed. Inspect your client’s MCP status, reconnect if needed, and start a new conversation. Installing workflow skills alone does not create a working connection.

If only one capability is missing, check tool availability. Do not reinstall the entire client to recover one disabled tool.

Authentication fails

For OAuth, use the client’s reconnect or sign-in action. For API keys, check that the header uses Authorization: Bearer …, that the key has not been revoked, and that an environment-variable reference is visible to the process running the client.

Inspect duplicate Simplified entries and their scopes before changing configuration. Update the affected entry instead of deleting unrelated credentials or plugins.

The wrong workspace or no matching resource appears

Call api_getWorkspaceInfo and api_listTeamspaces. Verify the credential’s workspace and the space_id passed to the failing tool. A teamspace ID cannot grant access to another workspace.

List the relevant accounts, projects, or boards again. Check pagination before concluding a named resource is absent.

A file cannot be used

A local path is not accessible to the hosted connector. Follow Assets and uploads. For remote files, check that the link points to downloadable bytes and is still accessible. Retrieve the asset again if its signed URL has expired.

Generation rejects settings or returns an unexpected result

Read the selected model’s current field schema. Check required inputs, supported dimensions and durations, reference formats, and credit balance. Do not assume every model supports the same settings.

A request times out

Keep any resource or job IDs and use Jobs and results to inspect the existing operation. Do not immediately repeat a publish, create, or generation request.

A post is not visible on the platform

Read the post’s latest status through social_getSocialMediaPosts. Check the selected account, scheduled time and timezone, and any platform error. A stored draft or accepted schedule is not a published post.

Ask for help with enough context

Include the client, tool name, time of failure, resource/job ID, teamspace, and sanitized error message. Remove API keys, authorization headers, and signed upload URLs. These details help distinguish a connection problem from a particular operation’s failure.