The Socifyr MCP server exposes the SDK as tools any Model Context Protocol client can call. Connect it once and your AI assistant can post, schedule, manage drafts, fetch analytics, and more — all in plain English.

Install

bun add -g @socifyr/mcp
# or
npm install -g @socifyr/mcp

Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "socifyr": {
      "command": "socifyr-mcp",
      "env": {
        "SOCIFYR_API_KEY": "sk_...",
        "SOCIFYR_WORKSPACE_ID": "..."
      }
    }
  }
}

Restart Claude Desktop. The Socifyr tools appear in the tools picker.

Configure Cursor / Windsurf / Continue

These clients use a similar mcp.json. Example for Cursor:

{
  "mcpServers": {
    "socifyr": {
      "command": "socifyr-mcp",
      "env": {
        "SOCIFYR_API_KEY": "sk_...",
        "SOCIFYR_WORKSPACE_ID": "..."
      }
    }
  }
}

Self-hosted

Set SOCIFYR_API_URL to point at your deployment:

{
  "env": {
    "SOCIFYR_API_KEY": "sk_...",
    "SOCIFYR_WORKSPACE_ID": "...",
    "SOCIFYR_API_URL": "https://api.mycompany.com/api"
  }
}

Verifying

In Claude, just ask:

"List my Socifyr connections"

It should call list_connections and read back your slugs.

"Post 'just shipped a new feature' to LinkedIn and X"

It'll resolve your slugs and call post_text.

What tools are available

See MCP Tools for the full list of 12 tools.

Limitations

• stdio transport only — runs as a subprocess of the MCP client, not over HTTP
• No streaming — uploads block until the API returns (typically < 5 seconds)
• Workspace is fixed — set at startup via SOCIFYR_WORKSPACE_ID. To switch workspaces, restart with a different env var.