mcp-remote in claude_desktop_config.json.
Social media studio (powered by So-me Studio) connects Claude through
https://api.so-me.studio/mcp/claude with OAuth sign-in. The Claude Connectors Directory
listing and the Social media studio plugin use this URL. Custom connectors may still use
https://api.so-me.studio/mcp with an X-API-Key (sk_live_... from
Settings > API Access in So-me Studio).Social media studio connector (OAuth)
1
Add the connector
In Claude go to Customize > Connectors. Open Social media studio from the
directory, or select Add custom connector and enter the name
Social media studio
and the URL https://api.so-me.studio/mcp/claude.2
Sign in
Select Connect. Claude opens the Social media studio sign-in page. Sign in with your
account, check the workspace, and allow access. No API key is needed.
3
Verify
Open a new conversation and ask Claude to list your connected accounts or draft a post.
Option 1: Connectors UI (recommended)
1
Open Connectors
In Claude Desktop go to Settings > Connectors > Add custom connector.
2
Enter the server details
3
Authenticate
Prefer OAuth when prompted (signs in with your Social media studio account). Alternatively,
add an HTTP header
X-API-Key with your key (sk_live_...), then save.4
Verify
Open a new conversation. Social media studio tools now appear in the tools menu — ask Claude
to list your posts or create a new one.
Option 2: mcp-remote bridge
If your build of Claude Desktop edits servers through the config file, bridge the remote HTTP server withmcp-remote. The classic
claude_desktop_config.json only launches local (stdio) commands, so the URL and header are
passed to the bridge.
1
Open the config file
Go to Settings > Developer > Edit Config in Claude Desktop, or open the
file directly:
2
Add the MCP server
claude_desktop_config.json
3
Restart Claude Desktop
Save the file and fully quit and reopen Claude Desktop for the changes to take effect.
4
Verify
Claude will now have access to Social media studio tools in your conversations. Ask it to list your
posts or create a new one.
Troubleshooting
401 / Missing X-API-Key header
401 / Missing X-API-Key header
The header name must be exactly
X-API-Key and the value must be an active key beginning
with sk_live_. With the mcp-remote bridge, double-check there is no stray space after
the colon.405 Method Not Allowed
405 Method Not Allowed
The Social media studio server runs in stateless Streamable HTTP mode and only accepts
POST
requests. mcp-remote and the Connectors UI both speak Streamable HTTP, so no SSE
configuration is required.