Claude Desktop

Claude Desktop only speaks stdio MCP today, while eWasl's server is HTTP. Bridge them with mcp-remote — a tiny official adapter that exposes any HTTP MCP server over stdio.

Prerequisites

• An eWasl API key with posts:read and posts:create permissions. Create one at app.ewasl.com/settings?tab=api_keys.
• A Professional or Enterprise plan (MCP/API access is gated).
• Node.js 18+ installed (for npx).

Configure

Open Claude Desktop's MCP config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the ewasl entry to mcpServers:

{
  "mcpServers": {
    "ewasl": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.ewasl.com/api/mcp",
        "--header",
        "Authorization: Bearer ewasl_YOUR_KEY_HERE"
      ]
    }
  }
}

Restart Claude Desktop. You should see ewasl listed under the MCP icon in the chat input.

Verify

Ask Claude:

List my connected social accounts.

If everything is wired correctly, Claude calls the list_connections tool and prints your accounts. If you get a 401, double-check the API key. If you get a 403, your plan doesn't include API/MCP access.

Available tools

See the MCP Overview for the full tool list (currently 11 tools spanning posts, connections, webhooks, and analytics timing).