Integrations
AI and automation integrations
OmniSocials connects to AI assistants and coding tools through two protocols: MCP (Model Context Protocol) and Agent Skills. Both use your OmniSocials API key and expose the same capabilities: create posts, upload media, list accounts, read analytics, and manage webhooks. Automation platforms (n8n, Make, Zapier) call the REST API with the same key, and agent frameworks connect to the hosted MCP server from your own code.
Pick the integration that matches the tool you use:
Claude
claude.ai, Claude Desktop, Claude Code
ChatGPT
Connect via OAuth, any ChatGPT plan
Grok
Custom MCP connector on grok.com
Muse
Meta's AI agent, connector built from a chat
Notion
Notion Custom Agents via MCP
OpenClaw
Personal AI assistant with MCP support
MCP Server
Cursor, Windsurf, and any MCP client
Agent frameworks
OpenAI Agents SDK, AI SDK, LangChain, Mastra, CrewAI
n8n
HTTP Request node, or an AI Agent over MCP
Make
HTTP app, Make a request module
Zapier
Webhooks by Zapier on a paid plan
Agent Skills
For non-MCP tools: Codex, Copilot, Gemini
MCP vs Agent Skills
Both approaches give an AI agent the same capabilities. They differ in how they connect.
| MCP Server | Agent Skills | |
|---|---|---|
| Works with | MCP-compatible clients (Claude, ChatGPT, Cursor, Notion, etc.) | Any AI tool that can run shell commands |
| Transport | Structured protocol (stdio or HTTP) | CLI + SKILL.md instruction file |
| Install | npx -y @omnisocials/mcp-server or remote URL | npx skills add OmniSocials/omnisocials-agent-skills |
| Best for | Tools with native MCP support | Codex, Copilot, Gemini CLI, and other non-MCP tools |
Both use the same API key and expose the same set of tools. You can run both in parallel with no conflict.
Coming soon
Raycast
Draft and schedule posts from Raycast
Slack
Real-time notifications and updates
Last modified on