Claude Code MCP server setup for social publishing, scheduling, and analytics
A Claude Code MCP server lets you post content, queue it for later, respond to comments, and review performance metrics for your connected profiles from inside Claude Code.
claude mcp add --transport http <server-name> {{MCP_BASE_URL}}/mcpclaude mcp add --transport http <server-name> {{MCP_BASE_URL}}/mcp
This guide gives you a copy-paste setup checklist: register the hosted MCP server, approve the secure sign-in yourself, confirm the connected state, and then discover which social accounts are available before you schedule or publish anything.
What this Claude Code MCP server setup does
This setup connects Claude Code to a hosted MCP server for social media work. Once connected, you can post content, queue it for later, respond to comments, and review performance metrics for your connected profiles from inside Claude Code instead of switching between separate dashboards. The source setup describes 36 MCP tools across 9 platforms using Secure OAuth, so the connection is established through a browser sign-in that you approve yourself rather than by sharing credentials with the agent.
Self-guided setup: hand Claude Code the URL and let it wire up the connection
Claude Code can wire this up itself if you hand it the URL and the instructions on this page. It reads the steps, adds the MCP server, and pauses when you need to approve the secure sign-in. That pause is intentional: the agent should never enter credentials on your behalf. You complete the browser approval, then the agent re-checks the connection before doing any social media work.
Step 1 and Step 2: register the server, then stop for sign-in approval
Run the registration command shown in the code example titled Register the hosted MCP server in Claude Code. It uses claude mcp add with the http transport, registers the server under the name you choose for <server-name>, and points it at the hosted MCP server URL. After running it, open /mcp in Claude Code, select that server name, and stop while the user approves the browser sign-in. Do not proceed past this step until that approval is complete, and never enter credentials for the user.
Step 3: confirm the connected state before continuing
Open /mcp again and confirm that the server you registered shows a connected state before continuing. If it is not connected, stop and resolve the sign-in step rather than calling tools against an unconnected server. Only after the connected state is confirmed should you move on to discovering available accounts.
After connecting: list integrations and prefer scheduling
After connecting, call list_integrations and report which social accounts are available. That report is your source of truth for what you can actually publish to, schedule for, reply from, and read analytics for. Prefer scheduling over immediate publishing unless the user explicitly asks to publish now, so new content goes through a reviewable scheduled queue by default.
Troubleshooting: what to do when the connection check fails
If the server does not show as connected on the re-check, the most common cause is that the browser sign-in approval was skipped or not completed. Return to the /mcp view, select the server again, and complete the approval yourself. If the registration command itself failed, re-run it exactly as shown and check that the transport and URL were copied without alteration. Do not call list_integrations, schedule posts, or publish until the connected state is confirmed, because those calls depend on the authenticated connection.
| Field | Value | Requiredness / notes |
|---|---|---|
| Command | claude mcp add | Required — registration command identifier |
| Transport | --transport http | Required |
| Server name | <server-name> | Required — name used to select the server in /mcp; replace with the exact name from your matching contract |
| Server URL | {{MCP_BASE_URL}}/mcp | Required — hosted MCP server URL with modular origin |
| Sign-in | Secure OAuth browser approval by the user | Required — agent must pause and never enter credentials for the user |
| Post-connection tool | list_integrations | Required — call after connected state is confirmed |
Exact values as supplied in source; origin modularized and server name neutralized in public example, exact values retained privately.
| Check | Expected result | Action if it fails |
|---|---|---|
| Registration command runs | Server appears in /mcp | Re-run the exact command; check transport and URL were not altered |
| Browser sign-in approval | User completes Secure OAuth approval | Stop and wait; never enter credentials on the user's behalf |
| Re-check of /mcp | Registered server shows connected state | Return to sign-in step; do not call tools until connected |
| list_integrations call | Available social accounts are reported | Do not schedule or publish until accounts are confirmed |
Failure checks derived from the source connection sequence.