AI assistant, MCP and API FAQ for Sociamonials
Sociamonials’ MCP connection gives compatible AI assistants access to supported social marketing tools. The Workspace API serves one brand workspace; the AgencyPro API serves assigned client workspaces. Access, approvals and connected social profiles determine what the assistant can actually do.
What is MCP, and why would I use it?
MCP is a way for a compatible AI assistant to discover and call tools. In Sociamonials, that lets you describe a supported marketing task in your assistant and have it use the connection to inspect context or take an authorized action. A practical starting point is validating a draft request before creating anything. MCP is a connection method; it does not remove the need for a content brief or a review process.
Should I use the Workspace API or AgencyPro API?
Use the Workspace API when the connection should operate one business’s workspace. Use the AgencyPro API when an active AgencyPro agency needs an integration across its assigned clients. Both offer REST and MCP access. Match the credential to the intended scope instead of sharing a broader agency credential for a single-client task.
Which accounts have API and MCP access?
The ordinary free trial does not include API or MCP access. Workspace API access is available to eligible paid and lifetime accounts; agency-resold client plans also need their API Access feature enabled. Agency-level access requires an active AgencyPro subscription and the appropriate assigned-workspace permissions. Account status and credential permissions still apply. Check eligibility for the exact account you intend to connect.
Does my Sociamonials plan include the AI assistant subscription?
No assistant subscription should be assumed to be included with Sociamonials API access. The assistant or automation service you connect may have its own subscription, usage limits or API charges. Choose that service separately and check its billing. Sociamonials permissions govern product actions; the assistant’s plan governs how you use that assistant.
What are useful AI-agent workflows for a small business?
Start with a narrow recurring task: inspect the current brand context, prepare a weekly content draft, validate it for the intended profiles, or retrieve available performance reports for a review meeting. An agency can repeat the process with separate client briefs and permissions. Verify that the required tool and permission exist before making it a recurring promise. See an actual validation example and a reusable prompt.
Can I require approval before posts go out?
The product supports approval-aware publishing workflows. Configure the applicable approval rules and make the assistant follow them; a prompt alone is not an access control. A saved draft, a validation response and an approval decision are different states. Our rehearsal did not submit a post for approval, and a draft response saying requires_approval: false does not establish permission to publish that content.
Does a successful validation mean a post was published?
No. validate_social_post checks the request without creating or publishing a post. A profileless draft can validate before any social destination is selected. Scheduling validation additionally needs an eligible destination and other required fields. After a real publishing action, inspect its recorded state and eventual delivery result; do not treat a successful draft check as proof of delivery.
How do I start safely and get useful work done?
Follow the relevant Workspace API or AgencyPro API setup instructions. Keep credentials in your assistant’s connection settings, not in a public prompt. For a Workspace API connection, confirm the one workspace it can access; for AgencyPro, list assigned workspaces and select the intended client. Check current context and permissions, then validate one draft. Add creation, approvals and scheduling only when you have defined who authorizes each action. Repeat a successful workflow weekly before expanding it.
Explore AgencyPro for client automation Read one-brand API setup