Loading...
Please wait while we prepare your content
Connect your AI coding agent to So-me.studio using the Model Context Protocol (MCP). This guide covers setup instructions for every major AI agent.
https://api.so-me.studio/mcpX-API-Key header.Once connected, your AI agent can call these 8 tools:
list_posts
List scheduled/published posts with filtering by status and platform
get_post
Get a single post by ID with full details
create_post
Create a new post targeting any connected platform
schedule_post
Schedule an existing post for future publishing
delete_post
Delete a post by its unique identifier
generate_caption
Generate an AI caption optimized for a specific platform and tone
generate_and_schedule
Generate AI content, create a post, and schedule it in one call
get_analytics_summary
Fetch workspace analytics: posts by status, platform, and trends
Anthropic's agentic coding tool in your terminal
Config: CLI command or .mcp.json
claude mcp add --transport http so-me-studio \
https://api.so-me.studio/mcp \
--header "X-API-Key: YOUR_API_KEY"Alternative: .mcp.json
{
"mcpServers": {
"so-me-studio": {
"type": "http",
"url": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Place this file in your project root for project-scoped access, or at ~/.claude/.mcp.json for global access.
Anthropic's desktop application for Claude
Config: claude_desktop_config.json
{
"mcpServers": {
"so-me-studio": {
"url": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Config file location — macOS: ~/Library/Application Support/Claude/claude_desktop_config.json | Windows: %APPDATA%\Claude\claude_desktop_config.json
AI-first code editor built on VS Code
Config: .cursor/mcp.json
{
"mcpServers": {
"so-me-studio": {
"url": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}OpenAI's coding agent for your terminal and IDE
Config: ~/.codex/config.toml
codex mcp add --transport http so-me-studio \
https://api.so-me.studio/mcp \
-H "X-API-Key: YOUR_API_KEY"Alternative: config.toml
[mcp_servers.so-me-studio]
url = "https://api.so-me.studio/mcp"
[mcp_servers.so-me-studio.env_http_headers]
X-API-Key = "SO_ME_API_KEY"When using env_http_headers, set the SO_ME_API_KEY environment variable in your shell with your actual API key.
AI-powered IDE by Codeium with Cascade agent
Config: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"so-me-studio": {
"serverUrl": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}GitHub Copilot agent mode with MCP support
Config: .vscode/mcp.json
{
"servers": {
"so-me-studio": {
"type": "http",
"url": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Google's AI agent for your terminal
Config: ~/.gemini/settings.json
gemini mcp add --transport http so-me-studio \
https://api.so-me.studio/mcp \
-H "X-API-Key: YOUR_API_KEY"Alternative: settings.json
{
"mcpServers": {
"so-me-studio": {
"httpUrl": "https://api.so-me.studio/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Place in ~/.gemini/settings.json for global access, or .gemini/settings.json in your project root for project-scoped access.
Once connected, your agent can post to all platforms you have linked in your So-me.studio dashboard:
Authentication failed / 401 Unauthorized
Double-check your API key is correct and active. Make sure the header is exactly "X-API-Key" (case-sensitive). Generate a new key from Settings > API Access if needed.
SSE / GET requests return 405
So-me.studio's MCP server runs in stateless mode using Streamable HTTP transport. Only POST requests are supported. Make sure your agent is configured with HTTP transport, not SSE.
Rate limit exceeded
MCP tool calls are rate-limited based on your subscription plan. Upgrade your plan or wait before retrying. Check your usage in Settings > MCP.
Credits exhausted
Each MCP tool call consumes credits. Check your remaining credits in Settings > MCP and upgrade your plan if needed.
Connection timeout
If your agent times out during connection, increase the timeout setting in your MCP configuration. A value of 30000ms (30 seconds) is recommended.
If you run into any issues setting up MCP, reach out to our support team or check the API docs for more details.