Verify your setup

This workflow confirms that Sociality MCP is connected correctly, your workspace data is accessible, and your client can run real queries before moving into production workflows. The first three steps do not use MCP credits. The final step runs a live stats query and will use credits according to your selections.

The goal is to finish with a verified MCP setup that is ready for agent workflows, internal copilots, reporting assistants, benchmarking flows, and custom tools powered by Sociality.io intelligence.

Step 1: Check your owned accounts

Goal: Confirm that your client is authenticated and can access the social accounts connected to your workspace.

Call:

social_accounts_list

Use the response to check:

• at least one owned account is returned
• account names and channels look correct for your workspace
• account IDs are visible for use in future queries

If nothing is returned, your OAuth connection may be incomplete or your workspace has no connected accounts yet.

Step 2: Check your tracked competitors

Goal: Confirm that your workspace has accessible tracked competitor profiles.

Call:

social_competitors_list

Use the response to check:

• at least one competitor is returned
• competitor names and channels look correct
• competitor IDs are visible for use in future queries

If you have no competitors set up yet, you can add one using social_competitors_create and a public profile URL.

Step 3: Review available tools

Goal: Confirm which tools your MCP client has loaded and understand what each one does before running analysis workflows.

Ask your MCP client to list the available tools. In most clients — such as ChatGPT, Claude, or Gemini — you can do this with a prompt like:

What tools do you have available from Sociality?

Use the response to verify the following tools are loaded and to understand their credit usage:

Discovery and setup (no credits)

• social_accounts_list — list owned accounts
• social_competitors_list — list tracked competitors
• social_competitors_create — add a new competitor by profile URL

Account analytics (uses credits)

• social_account_stats_list — fetch account-level stats for a given date range and aggregation period
• social_account_posts_list — fetch published posts for an owned account

Competitor analytics (uses credits)

• social_competitor_stats_list — fetch competitor-level stats for a given date range and aggregation period
• social_competitor_posts_list — fetch published posts for a tracked competitor

If any of these tools are missing, check your client configuration and confirm the Sociality MCP server is connected correctly.

Step 4: Run a test stats query

Goal: Confirm that data flows end to end by running a real stats query against an account or competitor from your workspace.

Using an account ID from Step 1:

social_account_stats_list
  account_id: <id from Step 1>
  since: 2026-06-17
  until: 2026-06-24
  period: day

Or using a competitor ID from Step 2:

social_competitor_stats_list
  competitor_id: <id from Step 2>
  since: 2026-06-17
  until: 2026-06-24
  period: day

Use the response to check:

• stats are returned for the expected channel
• metric fields are present and populated
• daily breakdown is visible across the date range

Final step: Confirm your first milestone

You have completed this setup check when you can confirm:

• MCP client is connected
• OAuth is working
• At least one owned account is listed
• At least one tracked competitor is listed
• All expected tools are loaded and credit usage is understood
• A live stats query returned data successfully

After this, your MCP setup is ready to use Sociality.io intelligence to support broader workflows through AI agents and custom tools.