Claude Code

Social media studio’s MCP server uses Streamable HTTP transport and authenticates with an X-API-Key header. Claude Code supports HTTP MCP servers natively.

You need an API key (format sk_live_...) to connect. Generate one from Settings > API Access, or see Authentication.

Setup

Run the CLI command

Open your terminal and run:

claude mcp add --transport http so-me-studio \
  https://api.so-me.studio/mcp \
  --header "X-API-Key: sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Verify the connection

Run /mcp in your Claude Code session. You should see so-me-studio listed as connected, along with the available tools.

Start using it

Ask Claude Code to create or schedule posts. For example:

Schedule a LinkedIn post about our new product launch for tomorrow at 9am

Alternative: .mcp.json

For project-scoped (team-shared) access, configure via a .mcp.json file in your project root:

.mcp.json

{
  "mcpServers": {
    "so-me-studio": {
      "type": "http",
      "url": "https://api.so-me.studio/mcp",
      "headers": {
        "X-API-Key": "sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

For access across all your projects, add the server at user scope instead:

claude mcp add --transport http so-me-studio \
  --scope user \
  https://api.so-me.studio/mcp \
  --header "X-API-Key: sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Scopes

Scope	Flag	Stored In	Use Case
Local (default)	`--scope local`	`~/.claude.json`	Private to you, current project only
Project	`--scope project`	`.mcp.json` in project root	Team-shared config (check into version control)
User	`--scope user`	`~/.claude.json`	Private to you, available across all your projects

If you commit a .mcp.json to version control, keep your real API key out of it. Use a placeholder and share the key through a secret manager instead.

Troubleshooting

so-me-studio shows as failed in /mcp

Confirm the transport is http (not sse). The Social media studio server runs in stateless Streamable HTTP mode and only accepts POST requests — SSE/GET connections return 405 Method Not Allowed.

401 / Missing X-API-Key header

The header name must be exactly X-API-Key (case-insensitive) and the value must be an active key beginning with sk_live_. Re-add the server with the corrected --header.

MCP Server

Other Agents

Setup

Alternative: .mcp.json

Scopes

Troubleshooting

​Setup

​Alternative: .mcp.json

​Scopes

​Troubleshooting

Setup

Alternative: .mcp.json

Scopes

Troubleshooting