Common setup issues

If your client is connected but the setup check does not look right, the issue is usually related to authentication, workspace access, available data sources, capabilities, or result limits. Use this section after completing the client connection steps and before moving into larger workflows.

OAuth does not complete

If authorization fails, returns you to the client without completing setup, or later becomes stale, reconnect Sociality MCP from your MCP client. This can happen when the OAuth window is closed too early, or the client does not complete the redirect back from Sociality.io correctly.

To resolve it, start the connection again from your MCP client, sign in with the Sociality.io account you want to use, approve the requested access, and wait until the client confirms that the server is connected.

If the issue continues, remove the existing Sociality MCP connection from your client and add it again from the beginning.

Workspace looks incorrect

If social_workspace_context returns an unexpected team, user, or credit status, you may be connected through a different Sociality.io account or workspace than intended. This can happen if you have access to more than one Sociality.io account, belong to multiple teams, or authorize MCP while signed in with a different browser session than the one you normally use.

To resolve it, check the team and user information returned by social_workspace_context. If it does not match the workspace you want to use, disconnect Sociality MCP from your client, sign out of the incorrect Sociality.io account if needed, then reconnect and authorize with the correct account and workspace context.

Accounts or competitors missing

This issue usually appears in one of two ways: MCP returns no accounts or competitors, or it returns a list that does not match what you expected.

1. No accounts or competitors returned

First, confirm that the selected Sociality.io workspace has owned accounts or tracked competitors available to your user.

If those data sources exist in Sociality.io but MCP still returns no results, read social_workspace_context and confirm that your MCP connection is using the correct Sociality.io account, workspace, and user context.

2. Unexpected accounts or competitors returned

When MCP returns a list, but the accounts or competitors are not the ones you expected, you may be connected to the wrong workspace or using a Sociality.io user without access to the expected data sources.

Read social_workspace_context and confirm the active workspace and user context. If the workspace or user context is incorrect, reconnect Sociality MCP with the correct Sociality.io account.

Capability mismatch

Use social_platform_capabilities as the source of truth for supported channels, features, metric names, metric descriptions, and aggregation behavior.

When a channel, feature, or metric you used before no longer appears in the capability list, check the latest documentation or changelog to confirm whether it is still supported.

After checking the latest updates, contact us with the exact platform, data type, metric name, and expected behavior if the capability still looks incorrect.

Tools or prompts unavailable

Some MCP clients may not show every tool, resource, or prompt supported by Sociality MCP. Refresh or reconnect the Sociality MCP server in your client to reload the available MCP capabilities. If prompts are missing, check whether your MCP client supports MCP prompts, because prompt support can vary by client.

List results look incomplete

social_accounts_list and social_competitors_list may return paginated results when there are many available accounts or competitors.

If the list looks shorter than expected, check whether the response includes pagination information before assuming items are missing.

You can also narrow the list with available filters, such as channel, name, or page.