MCP Server
The QiQ Social MCP (Model Context Protocol) server lets AI assistants like Claude manage your social media automations, create and publish posts, and interact with your workspace — all through natural language.
What is MCP?
Model Context Protocol is an open standard that allows AI assistants to securely connect to external tools and data sources. With the QiQ Social MCP server, you can control your entire content pipeline from Claude Desktop, Claude Code, VS Code, or any MCP-compatible client.
Available Tools
| Tool | Description |
|---|---|
list_workspaces | List all workspaces you have access to |
list_automations | List automations in a workspace |
get_automation | Get details of a specific automation |
create_automation | Create a new automation with scheduling and channel targeting |
update_automation | Update automation settings |
delete_automation | Delete an automation |
run_automation | Trigger content generation immediately |
list_connections | List platform OAuth connections |
list_channels | List publishing channels (Facebook pages, Telegram groups, etc.) |
list_posts | List posts with status and automation filters |
get_post | Get post details including content and metrics |
create_post | Create a draft post for a channel |
update_post | Edit a draft post’s content |
delete_post | Delete a draft post |
publish_post | Publish a post to its platform |
list_sources | List RSS feed sources |
create_source | Add an RSS feed source |
delete_source | Remove an RSS feed source |
validate_rss | Validate an RSS feed URL |
text_assist | AI text enhancement (proofread, rephrase, generate) |
media_assist | Search stock photos or generate AI images |
generate_hashtags | Generate platform-optimized hashtags |
list_assets | List media library assets |
list_labels | List workspace labels |
get_subscription_status | Check plan and usage limits |
Installation
No API keys or configuration needed — the server connects to QiQ Social automatically.
Claude Desktop
Edit your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"qiq-social": {
"command": "npx",
"args": ["-y", "@qiq/mcp"]
}
}
}Claude Code
claude mcp add qiq-social -- npx -y @qiq/mcpVS Code
Add to .vscode/mcp.json:
{
"servers": {
"qiq-social": {
"command": "npx",
"args": ["-y", "@qiq/mcp"]
}
}
}Remote (HTTP)
If you prefer not to install anything locally, you can connect to the hosted MCP server at mcp.qiq.social.
Claude Desktop — edit your config file:
{
"mcpServers": {
"qiq-social": {
"type": "url",
"url": "https://mcp.qiq.social/mcp"
}
}
}VS Code — add to .vscode/mcp.json:
{
"servers": {
"qiq-social": {
"type": "http",
"url": "https://mcp.qiq.social/mcp"
}
}
}How It Works
The MCP server supports two transport modes:
- Local (stdio): Runs on your machine via
npx. Your AI assistant spawns and communicates with the process directly. - Remote (HTTP): Hosted at
mcp.qiq.social. Your AI client connects over HTTP using the Streamable HTTP transport.
Both modes connect to the same QiQ Social backend with built-in credentials — no API keys needed.
AI Assistant ←→ MCP Server (local or remote) ←→ QiQ Social API- Your AI assistant connects to the MCP server (spawns locally or connects via HTTP)
- The server connects to QiQ Social using the built-in API credentials
- Tools execute queries and operations on your behalf
- Results are returned to the assistant as structured data
Automation Types
When creating automations, use these types:
| Type | Description | Requires Topic |
|---|---|---|
write_social | AI-generated social media posts | Yes |
write_blog | AI-generated blog articles | Yes |
rss_social | Repurpose RSS feed items as social posts | No |
rss_blog | Repurpose RSS feed items as blog articles | No |
rss_digest_blog | Digest multiple RSS items into one blog post | No |
Post Content Structure
Social Posts
{
"content": "Your post text here",
"media": [
{ "type": "image", "url": "https://example.com/photo.jpg" }
]
}Blog Posts (WordPress, Webflow)
{
"title": "Article Title",
"content": "<h2>Heading</h2><p>HTML content...</p>",
"excerpt": "A short summary",
"tags": ["marketing", "ai"],
"media": [
{ "type": "image", "url": "https://example.com/hero.jpg" }
]
}Discord Posts (with embed)
{
"content": "Check out this article!",
"embed": {
"title": "Article Title",
"description": "Article summary",
"url": "https://example.com/article"
}
}Platform Constraints
Each channel placement has character limits and media constraints:
| Platform | Placement | Max Characters | Max Media |
|---|---|---|---|
instagram_account | 2,200 | 10 | |
facebook_page | 63,206 | 80 | |
linkedin_profile | 3,000 | 20 | |
| X | x_profile | 280 | 4 |
| Telegram | telegram_channel | 4,096 | 10 |
| Discord | discord_channel | 2,000 | — |
| Threads | threads_profile | 500 | 10 |
pinterest_board | 500 | 1 | |
| Bluesky | bluesky_profile | 300 | 4 |