How to Connect SocialPilot With Claude Using MCP Server?
The SocialPilot MCP Server changes how your social media workflow runs.
Instead of creating content in AI and then manually setting it up in SocialPilot, you can define your workflow once inside Claude and let it carry out the execution for you. Posts can be created, scheduled, reviewed, and managed directly through your SocialPilot account without repeating the same steps every time.
This setup connects your SocialPilot account to Claude so your workflow moves from idea to published post in one continuous flow. Both methods below connect your SocialPilot account to Claude. The difference is how authentication is handled.
In this Article
- How to Set up MCP in Claude App by Signing Into SocialPilot?
- How to Set up MCP in Claude App Using Your SocialPilot API Key?
- How to Set Up MCP in Claude Code Using Terminal?
- How MCP Works With SocialPilot?
- What You Can Do With MCP in SocialPilot?
- Supported Actions and Capabilities
- Example Prompts to Use in Claude
How to Set up MCP in Claude App by Signing Into SocialPilot? (Recommended)
-
Open Claude and click Customize from the left sidebar.

-
Go to Connectors.

-
Click the + (plus) icon and select Add custom connector.

- Enter a name for your connector.
-
Paste the following URL and click Add:
https://mcp.socialpilot.co/mcp

After adding the connector:
-
Select the SocialPilot connector from the list and click Connect.

-
Sign in using your SocialPilot email and password.

Once connected, your SocialPilot account becomes available inside Claude for execution.
How to Set up MCP in Claude App Using Your SocialPilot API Key? (Advanced)
Step 1: Copy your API Key from SocialPilot
- Log in to your SocialPilot account.
- Click your profile icon in the top-right corner.
-
Go to Security.

-
Scroll to the API Key section.

- Copy your API key.
Step 2: Add your API key to the MCP connection in Claude
-
Open Claude and click Customize from the left sidebar.

-
Go to Connectors.

-
Click the + (plus) icon and select Add custom connector.

- Enter a name for your connector.
-
In the connector URL field, paste the following format:
https://mcp.socialpilot.co/{{API_KEY}}/mcp
(Replace
{{API_KEY}}with the API key you copied earlier.) - Click Add.
After adding the connector:
- Select the SocialPilot connector.
- Click Connect.
This URL uses your API key to authenticate the connection instead of a login.
Note:
API key authentication is optional and mainly used for custom workflows or development setups. For most users, signing in directly is the simpler option.
How to Set Up MCP in Claude Code Using Terminal?
You can also connect SocialPilot’s MCP server to Claude Code using a terminal-based setup. This is useful if you’re working in a local development environment or building custom workflows.
Before you begin make sure you have:
- Claude Code installed and set up.
-
Access to your SocialPilot account or API key.
Step 1: Choose Your Authentication Method
You can connect using either:
- Login-based URL (recommended)
https://mcp.socialpilot.co/mcp
- API key-based URL
https://mcp.socialpilot.co/{{API_KEY}}/mcp
Replace {{API_KEY}} with your actual API key if you’re using this method.
Step 2: Add the MCP Server in Claude Code
In your terminal, run:
claude mcp add socialpilot https://mcp.socialpilot.co/mcp
If you’re using an API key:
claude mcp add socialpilot https://mcp.socialpilot.co/YOUR_API_KEY/mcp
This registers the SocialPilot MCP server with Claude Code.
Step 3: Authenticate Your Connection
- If you used the login-based URL, a browser window will open
- Sign in using your SocialPilot email and password
If you used the API key, authentication is handled automatically.
Step 4: Verify the connection
Run:
claude mcp list
You should see the SocialPilot MCP server listed.
How MCP Works With SocialPilot?
MCP follows a simple, repeatable workflow that mirrors how social media work actually happens.
Discover
Identify available accounts, groups, and workspace structure before taking action.
Create
Generate posts, save drafts, or schedule content across one or more accounts.
Review
Inspect drafts and post details before publishing.
Monitor
Track what is scheduled, published, failed, or missed.
Refine
Adjust, fix, and continue workflows based on real-time status.
This allows AI agents to operate continuously with awareness of both content and execution.
Supported Actions and Capabilities
| Category | Capability | Description |
|---|---|---|
| Account and Workspace Context | UserInfo | Retrieve details of the current user |
|
|
AccountList | View all connected social accounts and filter by platform, group, or client |
|
|
GroupList | Access all account groupings used for bulk actions |
| Post Creation and Drafting | CreatePost | Create and schedule posts across one or multiple accounts |
|
|
CreateDraft | Save posts as drafts for later review or publishing |
| Draft Management | DraftList | View all saved drafts across accounts |
|
|
ViewDraft | Retrieve details of a specific draft |
| Post Monitoring and Status | AccountQueued | View all scheduled or queued posts |
|
|
DeliveredPosts | View posts that have already been published |
|
|
ErrorPosts | Identify posts that failed to publish |
|
|
UnscheduledPosts | Track posts that missed their scheduled time |
|
|
ViewPost | Retrieve full details of a specific post |
What You Can Do With MCP?
With MCP, AI agents can execute end-to-end social media workflows across your SocialPilot account.
Create and Schedule Content
Generate posts and publish them across selected accounts, groups, or clients.
Manage Drafts
Save, review, and update drafts before publishing.
Track Post Status
Check what is scheduled, published, failed, or missed in real time.
Retrieve Post Details
Access full context for any post when needed.
Work Across Accounts and Groups
Operate across multiple accounts with awareness of how they are structured.
Example Prompts to Use in Claude
Use these prompts in Claude to execute publishing tasks across your SocialPilot accounts, from creating posts to reviewing drafts and tracking delivery.
| Category | Prompts |
|---|---|
| Creating and Publishing | Schedule this product launch post to all LinkedIn accounts in Client A for tomorrow at 10 AM. |
|
|
Publish this weekend offer post to Instagram and Facebook at 6 PM today. |
|
|
Create and schedule a new product update post for all accounts in Group X for Monday morning. |
| Drafting and Reviewing | Save this campaign announcement as a draft for all LinkedIn accounts in Client B. |
|
|
Show all drafts created this week that are waiting for review. |
|
|
Update the latest draft for Client B with a shorter caption and add relevant hashtags. |
| Monitoring and Troubleshooting | What posts are scheduled across all accounts for today? |
|
|
Show posts that failed to publish in the last 7 days. |
|
|
Which posts missed their scheduled time this week? |
|
|
Show all posts currently in queue for Client A. |
| Account and Context Access | What social accounts are connected to this workspace? |
|
|
Show all accounts under Client Y. |
|
|
List all groups available and the accounts within each group. |
| Workflow Execution | Create a weekend discount post and schedule it across all Instagram and Facebook accounts in Client A for the next three days at 10 AM. |
|
|
Generate a product update post for LinkedIn and save it as a draft for Client B for review. |
|
|
Create a promotional post for Group X and schedule it across all accounts for Friday at 5 PM. |
|
|
Check all scheduled posts for today and highlight any that failed or missed their timing. |
Permissions and Access
MCP operates within the existing structure of your SocialPilot account.
- AI agents can only access accounts and data already available to the user.
- Account-level permissions and group structures remain unchanged.
- No additional access is granted beyond what is already configured.
This ensures that workflows remain controlled and consistent.
Notes
- You only need to connect once to start using MCP.
- All actions follow your existing account permissions in SocialPilot.
- API key authentication remains supported for advanced use cases.







