Skip to content
Webixso MCP Connector

Webixso MCP Connector

The Webixso MCP Connector lets Claude work with Webixso over the Model Context Protocol (MCP). After you connect and sign in, Claude can list your linked Instagram, Facebook, LinkedIn, X, Pinterest, TikTok, YouTube, Reddit, and other Webixso-supported accounts; create and schedule posts; upload images for public URLs; and (if you allow it) render design templates and publish them.


Before you start

To use the Webixso MCP Connector, you’ll need:

  • Claude (web or desktop) with support for Connectors and/or remote MCP, depending on how you connect—see below.
  • A Webixso accountsign up free of charge.
  • Social accounts connected inside Webixso—the connector can only post through profiles you have already linked in the Webixso app.
  • A normal browser session for the first OAuth sign-in and permission screen.

Availability: Registering is free. Credits and plan quotas apply to publishing and some actions; free and paid plans offer different limits. Check webixso.com for current pricing and quotas.

Availability: Some Claude features (for example Connectors in the Claude app) may require a paid Claude plan. Follow the options below that match your product.


Official endpoint and OAuth client (required)

For the Webixso directory connector, or when the form asks for a custom connector, use these values unless Webixso announces a change:

Field Value
MCP server URL https://mcp.webixso.com/mcp
Alternative (HTTP only if your environment requires it) http://mcp.webixso.com/mcp
OAuth client ID 7bce6589c373e88becea56e22752ff2must match exactly

If the connector asks for a client secret, use the value Webixso provides in your dashboard, connector email, or support. If Webixso documents say your tenant uses PKCE without a secret, leave the secret blank as instructed there.

Authorization server metadata (for debugging):
https://webixso.com/.well-known/oauth-authorization-server
(Replace webixso.com with your org’s app domain if different.)


Connect with Claude

Webixso’s MCP connector is documented for Claude only (Claude on the web / Claude app, plus the optional Claude Desktop advanced path below).

Claude (connectors—recommended)

This is the easiest path when Webixso appears in Claude’s connector browser or you add a custom connector with the fields above.

Availability: Connector availability in Claude may depend on your Claude plan and region. See Claude documentation.

  1. Open Claude (web or desktop).
  2. Start a new chat. Open Search and tools (or Manage connectors, depending on your Claude version).
  3. Choose Add connector / Browse connectors (or Custom connector if Webixso is not listed yet).
  4. Enter:
    • Name: for example Webixso
    • MCP server URL: https://mcp.webixso.com/mcp (or HTTP only if required)
    • OAuth client ID: 7bce6589c373e88becea56e22752ff2
    • Client secret if the form requires it and Webixso gave you one
  5. Complete the Webixso sign-in and Allow the requested permissions (read / post / design as shown).

Claude Desktop (MCP server—advanced)

Availability: Advanced setups vary by Claude Desktop version and OAuth support. Prefer Claude connectors above when possible.

Remote MCP via a local bridge often needs Node.js (LTS recommended) and npm. Install from nodejs.org if needed.

  1. Open Claude Desktop.
  2. Open settings (Ctrl + , on Windows, Command + , on macOS).
  3. Open Developer and Edit Config.
  4. Add a server block (example using mcp-remote to reach the hosted MCP URL):
{
  "mcpServers": {
    "Webixso": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.webixso.com/mcp"
      ]
    }
  }
}

If your flow still fails to attach OAuth tokens, use the Claude connector / custom connector path in Claude web instead, or see Anthropic’s MCP quickstart.


Check the connection

  1. In Claude, confirm Webixso (or your chosen name) appears under Search and tools / Connectors when relevant.

  2. Ask a simple question, for example:

    List my connected Webixso social accounts.

  3. Approve the tool call if prompted. If the list returns, OAuth and MCP are working.

Other quick tests:

  • “Upload this image for posting and give me the public URL.” (JPEG/PNG/GIF/WEBP only.)
  • “Draft a short post for my connected Facebook Page.” (Requires that account in Webixso.)

Usage ideas (like a quick-start)

  • Browse accounts: “Show my Instagram and LinkedIn accounts connected in Webixso.”
  • Publish now: “Post this caption and image to my Facebook Page.”
  • Schedule: “Schedule this text on LinkedIn for tomorrow at 10:00.”
  • Carousel: “Create a carousel on Instagram with these three image URLs and this caption.”
  • Design: “Render template [id] with these variables and publish to the accounts I choose.”

Troubleshooting

Symptom Try this
Authorization failed Client ID must be 7bce6589c373e88becea56e22752ff2. MCP path must be /mcp. Confirm client secret if your tenant uses a confidential client.
401 / MCP unauthorized Reconnect the connector; complete Webixso login and consent again.
Nothing to post to Connect the social account inside the Webixso app first.
Image rejected Use JPEG, PNG, GIF, or WEBP; respect size limits.
Too many requests Wait and retry; credits and burst limits protect the service.

Health check: Open https://mcp.webixso.com/health (or http://… if that’s all your environment allows). You should see a small JSON response with service status.


Support

Return to Webixso help and product home: webixso.com


Webixso may update endpoints or OAuth policy—prefer the version linked from webixso.com if this file diverges.