Skip to main content
Sprout Social is a Conditional, read-only CRM & Sales integration. It uses Sprout-hosted OAuth and MCP to analyze connected TikTok post performance and published insights.
Each customer workspace needs a Sprout OAuth client created from an eligible Sprout account. daoco keeps every workspace’s client secret and OAuth tokens separate.

​
Connect a customer workspace

You need a Sprout administrator who can access Global Features > API. Confirm that the customer’s use complies with their Sprout API agreement.
1

Open OAuth Client Management

In Sprout, open Settings > Global Features > API. Accept the Analytics API terms if prompted, then open OAuth Client Management.
2

Generate a user-based configuration

Choose Generate configuration and select User-based authentication.
3

Add the daoco redirect URI

Copy the exact OAuth redirect URI shown on the Sprout Social setup card in daoco and add it to the client’s allowed redirect URIs.
4

Enter the workspace OAuth credentials

In daoco, open Connections > Integrations > CRM & Sales > Sprout Social. Paste the customer’s client ID and client secret. The endpoint and scopes are already filled in.
5

Connect Sprout Social

Choose Save and connect, then sign in to the customer’s Sprout account and approve access.
The setup card reads the callback URI resolved by the daoco backend for the active deployment. By default it uses that deployment’s Convex HTTP endpoint. If MCP_TENANT_OAUTH_CALLBACK_URL is configured, the card displays that exact override instead.
daoco preconfigures these values, so customers do not need to enter them:
If Sprout explicitly approves a multi-tenant OAuth client for daoco, set MCP_SPROUT_SOCIAL_CLIENT_ID and MCP_SPROUT_SOCIAL_CLIENT_SECRET in the Convex deployment environment. Customers will then see a one-click OAuth connection instead of the credential form. Do not use this model without confirmation from Sprout.
If Global Features > API is missing, ask a Sprout account administrator to confirm your plan, role, and API access. Do not paste the OAuth client secret into chat, tickets, or customer-facing documentation.
See Sprout’s API setup documentation and hosted MCP connection overview for provider requirements.