Connect Wonda to Claude

What you get

The Wonda cloud twin lets Claude use your server-side social personas through Wonda tools. Claude can read search results, feeds, profiles, analytics, inboxes, and account health across LinkedIn, Reddit, X, and Instagram. It can also ask Wonda to take approved actions such as posting, replying, commenting, connecting, messaging, scheduling, and running bounded campaigns.

This is the cloud connector path. You do not need the Wonda CLI, a local browser, or an API key field in Claude.

Connect on Claude.ai web or Cowork

Add Wonda as a custom connector by URL:

https://prod-mcp-remote-mba3ghntzq-nw.a.run.app/mcp

In Claude, open Settings, then Connectors, then Add custom connector. Name it Wonda, paste the URL, and continue.

Claude opens Wonda's OAuth flow in the browser. Sign in with Wonda, choose the account or organization context you want Claude to use, review the consent screen, and approve access. Claude receives OAuth tokens for the Wonda MCP resource at https://api.wondercat.ai/.well-known/oauth-protected-resource/mcp. Your Wonda API key stays inside Wonda and is not shown to Claude or copied into the connector form.

This custom connector path does not require a Connectors Directory listing or Anthropic review. The Directory path is optional and skipped by default.

Connect on Claude Desktop

Claude Desktop can use the same remote connector when your Claude account has custom connector support. Add Wonda in Claude's connector settings, paste the same connector URL, and complete the OAuth grant in the browser.

Technical users can also run Wonda locally:

• Use the stdio MCP package with npx -y @degausai/wonda-mcp and your normal Wonda CLI authentication.
• Use the local wonda.mcpb Desktop Extension on macOS when you want platform actions to run through your on-device Wonda Automation Browser and local cookie store.

The local paths are useful for Claude Desktop and Claude Code. Claude web and Cowork need the remote connector.

Team and Enterprise

For Claude Team and Enterprise workspaces, an organization owner or connector admin may need to add and approve Wonda before members can use it. Add Wonda once as a custom connector, complete the Wonda OAuth grant, and approve it for the workspace.

In Wonda, paid organization seats use the organization's twin access and billing context when the OAuth grant is made from that organization. Members still act through their assigned Wonda permissions, spend limits, and platform account connections.

Consent and approvals

Wonda labels read tools as safe for Claude's Always allow mode. Read tools have zero write slots and cover retrieval such as feeds, profiles, inboxes, analytics, job status, twin health, and action allowance.

Write tools are labeled as needing approval. They request one or more server-side write slots depending on the action. Examples include comments, replies, direct messages, connection requests, follows, saves, votes, posts, schedules, and campaign runs.

Claude's consent setting is a client-side prompt. Wonda still enforces the server-side action gate, write-slot allowance, daily caps, cooldowns, account status, billing, and safety checks before anything is sent to a platform.

Autopilot or supervised mode

For supervised use, leave write tools in an ask-first mode. Claude will ask before it asks Wonda to act.

For hands-off workflows, allow a bounded campaign or schedule tool instead of approving each small action. A campaign approval lets Wonda run the requested loop server-side within the configured caps, cooldowns, and relevance checks.

Setting a write tool to Always allow does not mean unlimited action volume. Wonda still applies action allowances, spend limits, daily caps, cooldowns, paused-session checks, and platform health gates.

Onboard your platform accounts

The connector can only act through platform accounts that are already connected to the selected Wonda twin. If a platform session expires, Wonda will ask you to refresh it through the streamed login view before read or write tools continue.

Troubleshooting

• Claude asks you to connect again: complete the OAuth grant again from Claude's connector settings.
• A platform account needs auth: open the Wonda streamed login view for that twin and platform, then sign in.
• 402 responses: add credits or update billing.
• 423 responses: resume the paused twin or clear the account safety state in Wonda.
• 429 responses: wait for the action allowance, platform cooldown, or rate limit window to reset.

Connectors Directory

The Connectors Directory is not required for this connector. Wonda ships as a custom connector by URL, so users can connect without a Directory listing and without Anthropic contact.

If Wonda later chooses to request a Directory listing, that should be a separate go or hold decision after live connector verification has passed. The reviewer account must be owned by Wonda, must sit in a Team or Enterprise organization, and must have only Wonda-owned platform identities connected. Do not submit a Directory packet until the connector URL, OAuth metadata, redirect callbacks, read tools, write approvals, and reviewer credentials have all been verified.