Ocoya Social Media MCP. Manage profiles, posts, and automations via your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Ocoya Social Media MCP Server handles content scheduling, profile management, and workflow tracking across your social channels. It lets your AI client read user profiles, list all posts, view active automations, and manage multiple workspaces from one connection point.
What your AI agents can do
Get automation
Retrieves detailed information for one specific marketing workflow or automation.
Get me
Gets the basic profile and authentication info for the user currently running the agent.
Get post
Fetches all content details for a specific post using its unique ID.
Get a list or specific details about the overall workspaces configured in your Ocoya account.
List all connected social profiles or retrieve detailed information for one specific profile (e.g., Twitter, LinkedIn).
Retrieve a list of published posts or fetch the full details for a single post by its ID.
List all available marketing workflows and read the settings for specific automations using get_automation.
Authenticate your agent and get the current user's information within the Ocoya system.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Ocoya Social Media MCP Server: 9 Tools for Content Management
These nine tools let your agent read and write data across all aspects of your Ocoya marketing platform, from user settings to scheduled posts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Ocoya Social Media on Vinkius019dd12fget automation
Retrieves detailed information for one specific marketing workflow or automation.
019dd12fget me
Gets the basic profile and authentication info for the user currently running the agent.
019dd12fget post
Fetches all content details for a specific post using its unique ID.
019dd12fget profile
Retrieves full data and connection status for one social media profile (e.g., LinkedIn or Twitter).
019dd12fget workspace
Gets the specific details of a named workspace within your Ocoya account.
019dd12flist automations
Returns a list summary of all automations and workflows currently active in your account.
019dd12flist posts
Provides a paginated list of content posts, including both published and scheduled items.
019dd12flist profiles
Lists all social media profiles connected to your Ocoya account so you know what channels are live.
019dd12flist workspaces
Returns a list of every workspace configured in the Ocoya platform.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Ocoya Social Media, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Ocoya. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Sifting through dashboards for scheduled posts takes way too long.
Today, checking your content calendar means logging into the web portal. You click 'Workspaces,' then navigate to a specific campaign folder. Then you hit 'Posts' and filter by status—published, draft, or queued. It’s four clicks just to see what was supposed to go out yesterday.
With this MCP Server, your agent handles it all in one prompt. You ask for scheduled posts, and the `list_posts` tool returns a clean list of every post across every workspace you manage. You get data; you don't get clicks.
Ocoya Social Media MCP Server: Get full visibility into profile status.
Manually checking if your Twitter and LinkedIn connections are still active is a pain. You have to go through settings menus, check the connection status badge, and hope it hasn't broken overnight. It’s manual overhead you should never repeat.
Now, just ask for it. Running `get_profile(id='[specific id]')` gives you the live, structured data on that profile's health in seconds. You know instantly if everything is fine or if a connection needs fixing.
What you can do with this MCP connector
Yo. Look, this Ocoya Social Media MCP Server gives your AI client the straight dope on all your social media stuff—profiles, posts, and automated workflows. You don't wanna deal with a bunch of different dashboards; you just want one connection point that handles everything.
When you connect it, you get full access to manage your entire content marketing stack through your agent. It lets your client check out what profiles are linked up, see every post—whether it went live or's sitting there waiting to go out—and audit all the automations running in the background.
You’re talking about controlling multiple workspaces without logging into anything else.
Managing Workspaces and Profiles
Want a rundown of your whole account setup? Use list_workspaces to grab a list of every workspace you've got configured in Ocoya. If you need the nitty-gritty on one specific area, run get_workspace and give it the name, and it’ll spit out those detailed settings. To see what social channels are even connected, use list_profiles; this lists all your linked profiles so you know which accounts are ready to rock.
If you need deep details on a specific account—say, LinkedIn or Twitter—you run get_profile and it pulls back the full data and connection status for that one profile. It's how your agent knows if everything's legit and connected right.
Tracking Content and Posts
Dealing with content is a whole other ballgame. To get a comprehensive view of everything you've posted, use list_posts. This tool gives you a paginated list that includes both posts that are already published and those scheduled for the future. It’s your central feed.
If you only care about one piece of content—maybe you wanna check up on a specific campaign post—you use get_post and pass in its unique ID, and it returns all the content details for that single item. No guesswork required here.
Auditing Automations and Workflows
For the automated side of things, your agent can give you full visibility into what's running. To see a summary of every marketing workflow or automation active in your account, just run list_automations. That gives you the overview.
If you need to dive deep into one specific piece of tech, use get_automation. You feed it the name of the workflow, and it retrieves detailed information about that exact setup. This lets you see exactly how a particular automation is configured.
User Context
Finally, your agent needs to know who's running the show. To authenticate and get basic info on the user currently operating the system, run get_me. It confirms your identity and provides necessary authentication details within the Ocoya platform.
019dd12f-77eb-7310-a66b-4802c5c5a9c3 
How Ocoya Social Media MCP Works
- 1 Provide your API Key to Vinkius. Your AI client uses this key to authenticate with the Ocoya platform.
- 2 The agent calls a specific tool (e.g.,
list_workspaces). The server executes that function against the live Ocoya data. - 3 Your agent receives structured JSON data describing the profiles, posts, or automations you asked for.
The bottom line is: your AI client talks to us, we talk to Ocoya, and we send you clean data.
Who Is Ocoya Social Media MCP For?
This is for the Digital Marketing Operations Manager who spends too much time clicking between dashboards just to figure out what's actually scheduled. It's also for the Content Strategist who needs to verify profile connections or audit campaign workflows without logging into a web portal.
Uses list_workspaces and get_me to map out which accounts are connected and where the current content efforts live. They run daily audits using automation tools.
Calls list_profiles and then uses get_profile to check if a new social channel is set up correctly, or runs list_posts to pull historical data for pitch decks.
Needs to verify which posts are scheduled (list_posts) and whether the associated workflows are active using get_automation.
What Changes When You Connect
- Audit all workflows at once. Use
list_automationsto see every marketing workflow running without opening the web dashboard. - Check profile health immediately. Run
get_profileon a specific channel name to confirm connection status, which is faster than clicking through settings. - Get content history instantly. Call
list_poststo pull a summary of all scheduled and published posts for a campaign review. - See your current context. Use
get_mefirst to verify the agent is running under the correct user's permissions before executing major commands. - Map out your setup. Run
list_workspacesandlist_profilestogether to get a complete inventory of every site you manage through Ocoya.
Real-World Use Cases
Checking Campaign Status
A manager needs to know how many posts are ready for the upcoming holiday campaign. They ask their agent, which runs list_posts. The agent returns a list summary of all content statuses (drafted, scheduled, published), letting the manager see exactly what's done and what's left.
Debugging Automation Failure
An automated workflow stopped sending emails. Instead of hunting through logs, the agent runs get_automation using the workflow ID. This quickly reveals the last successful step or a specific error message, allowing for rapid fixes.
Client Onboarding Audit
A new client account needs to be reviewed before launch. The agent runs list_workspaces and then calls get_profile for each listed channel. This confirms that all required social profiles are connected and active.
Data Dump for Reporting
The analytics team needs a list of every post published last quarter. The agent uses list_posts to pull the historical data, providing structured, clean results that can be dropped right into a spreadsheet.
The Tradeoffs
Guessing the Scope
Telling the agent: 'Show me my posts.' The agent doesn't know which workspace or profile you mean, leading to an ambiguous error or a massive, useless data dump.
→
Always narrow the scope. First, run list_workspaces to confirm the correct context. Then, use get_workspace(name='[specific name]') before calling list_posts. This locks down the data set.
Ignoring User Context
Trying to run an action like 'Check my connection status' without first running get_me. The agent can't confirm whose account it's checking, and the call fails.
→
Start with get_me. This confirms your agent client is authenticated under the right user ID. It’s a necessary prerequisite for any sensitive operation.
Treating 'List' as Detail
Running list_profiles and assuming it gives you enough detail to fix an issue. The list only provides names, not the connection status or API key health.
→
If you need details, don't stop at the list. Use get_profile(id='[specific id]'). This pulls the full object data—the actual connection metrics and metadata you need.
When It Fits, When It Doesn't
Use this server if your primary job is managing content lifecycle across multiple social accounts (profiles, posts, automations). You need to audit what exists, check status, or retrieve bulk historical data. Don't use it if you are building a highly specific analytics report based on external metrics like ad spend—for that, you’d need a dedicated financial API gateway. If your goal is just writing content, your AI client handles that. But if the goal is publishing and scheduling, this is what you need. Always verify user context first using get_me before attempting to list anything.
Common Questions About Ocoya Social Media MCP
How do I see all my connected social media accounts with Ocoya Social Media MCP Server? +
You run list_profiles. This tool returns an inventory of every profile linked to your account, letting you know exactly which channels are currently managed.
Does the get_automation tool only show active workflows? +
No. You first use list_automations for a summary list, and then you call get_automation(id='...') to pull detailed information on any specific workflow, whether it's active or paused.
What is the difference between list_posts and get_post? +
list_posts gives you a summary view of many posts—useful for seeing campaign volume. get_post fetches the complete, deep data object for one specific post ID.
Can I check my user account info with get_me? +
Yes. Calling get_me verifies your current authentication credentials and provides basic user details, confirming your agent's context before you run other commands.
When I use the `get_workspace` tool, what scope of data does it retrieve? +
It retrieves metadata about the workspace itself, like its name, creation date, and owner. It won't pull post content or profile details; you need separate calls to list those specific assets.
If I use `get_profile` with an ID that doesn't exist, what happens? +
The tool immediately returns a clear error message. Your agent knows the Profile ID is invalid or inaccessible, stopping the workflow right there instead of failing silently.
What kind of parameters does `get_automation` require to run? +
It requires a unique automation identifier (ID) and must be called within an authenticated workspace context. This ensures your agent gets the exact workflow you're looking for.
When calling `list_posts`, how can I filter the results to narrow down my search? +
You typically pass optional filters like a date range or specific profile ID. This lets your agent pull only the posts you care about, instead of dumping every single post record.
Where do I find my API Key? +
Your API Key can be generated in the Ocoya Developer or Integrations settings page.
What access does this MCP need? +
It requires your API Key to access your profiles, workspaces, and posts.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.