How to Schedule Social Media Posts with Muse Code
Connect Meta’s terminal coding agent to PostDovo using MCP, then prepare drafts, check social accounts and schedule posts with natural-language prompts.
Want to manage a publishing calendar without opening a separate tab for each social network? Muse Code can communicate with PostDovo’s remote MCP server to access supported social media tools from your terminal.
PostDovo Starter costs $0/month and includes supported AI-agent connectivity and unlimited Single Post scheduling.
How Does Muse Code Connect to Social Media?
Muse Code is Meta’s coding agent for the terminal. It runs on Windows, macOS and Linux. Through the Model Context Protocol (MCP), it can connect to services such as PostDovo without requiring you to build an integration from scratch.
PostDovo provides this remote Streamable HTTP endpoint:
Unlike the regular Meta Muse personal agent, which relies on a custom-connector creation workflow for an unlisted service, Muse Code has a documented MCP configuration and login command. That makes this a distinct integration guide.
Reference: Meta’s Muse Code MCP documentation.
How to Connect Muse Code to PostDovo in 5 Steps
The first four steps use browser authorization. Step 5 is an optional token-based alternative; you don’t need both methods.
Install Muse Code and Sign In to Meta
Open your system terminal and use the official Meta installer. Choose the command for your operating system.
irm https://dev.meta.ai/install.ps1 | iex
curl -fsSL https://dev.meta.ai/install.sh | sh
Once installed, check that Muse Code is available:
muse --version
From a folder you trust, start Muse Code:
muse
On first use, Muse Code asks whether you trust the workspace, then offers browser sign-in or a Meta API key. Complete that sign-in before proceeding. This authorizes Meta model access, not PostDovo.
Already using Muse Code? Skip installation. If your model sign-in needs updating, type /login in an interactive session.
Add PostDovo to Muse Code Settings
Open your Muse Code settings file at ~/.config/muse/settings.json (on Windows, this is normally under your user home directory at .config\muse\settings.json).
Create the file if it doesn’t exist, then configure the PostDovo MCP server:
{
"schema_version": 1,
"mcp_servers": {
"postdovo": {
"transport": "streamable_http",
"url": "https://app.postdovo.com/mcp",
"mode": "optional"
}
}
}The schema_version value must be 1. The mcp_servers object holds your connections, while mode: optional means Muse Code can continue with a warning if PostDovo is unavailable instead of failing the whole run.
Already have a settings file? Preserve other settings and MCP servers. Add only the postdovo entry inside your existing mcp_servers object, and keep valid JSON syntax.
Different key in newer docs? Meta’s developer documentation also recognizes mcpServers with type: streamable-http. The older format above remains supported; don’t include both root keys in one file. If your installed version’s documentation expects the newer format, see the configuration example in Troubleshooting.
Sign In to PostDovo and Approve Access
In your regular terminal, run:
muse mcp login postdovo
Muse Code starts the remote MCP authorization process. When the browser flow is available, sign in to PostDovo if asked, review the permissions, and choose Approve.
Muse Code stores and refreshes the OAuth credentials for the MCP connection. If you use a headless environment, check muse mcp login --help for available options.
The initial Meta sign-in runs the Muse Code model. This step authorizes Muse Code to use your PostDovo workspace. You do not need a PostDovo access token for the browser OAuth method.
Verify the Connection and Available Tools
Start a fresh Muse Code process in a project folder:
muse
Inside the session, enter /mcp. Look for postdovo and its discovered tools.
If Muse Code retrieves the expected connected accounts, the MCP endpoint, authorization and at least one read-only operation are working. Check the actual tool response before moving to a write action.
Meta documents tool approvals for non-read-only operations, but MCP tools are not necessarily confined by Muse Code’s shell-command sandbox. Connect only services you trust and check approval requests carefully.
PostDovo requires a preview and your explicit approval for immediate publishing. Approved scheduled posts can publish automatically at their scheduled times.
Optional: Use a PostDovo Access Token Instead
Can’t complete browser authorization, or need a headless setup? Create a token under PostDovo → Access Tokens. PostDovo shows a newly created token once, so store it securely.
Replace the PostDovo entry in your existing settings file with an HTTP authorization header. The example below reads the token from an environment variable, rather than writing the secret into the JSON file:
{
"schema_version": 1,
"mcp_servers": {
"postdovo": {
"transport": "streamable_http",
"url": "https://app.postdovo.com/mcp",
"headers": {
"Authorization": "Bearer ${POSTDOVO_TOKEN}"
},
"mode": "optional"
}
}
}Set POSTDOVO_TOKEN in the environment from which you launch Muse Code:
export POSTDOVO_TOKEN="YOUR_POSTDOVO_TOKEN"
$env:POSTDOVO_TOKEN = "YOUR_POSTDOVO_TOKEN"
Replace the placeholder with your actual token and start a new Muse Code process. Do not post the token in a chat or commit it to a repository. Environment-variable values set this way apply to the current shell session and can be exposed through shell history; for ongoing use, prefer a trusted secrets-management method.
Run /mcp again and test the connected accounts. If the token setup fails, try the documented OAuth command from Step 3.
Video Tutorial: Connect Muse Code to PostDovo
Follow the installation, settings-file configuration, OAuth approval and read-only connection test in your video walkthrough.
Example: Schedule Three Days of Posts with Muse Code
Once the connection works, use this prompt to prepare distinct Facebook and LinkedIn captions. The request asks for the plan first—no content should be created or scheduled until you approve the next action.
Using PostDovo, prepare 3 days of text-only posts about https://postdovo.com for Facebook and LinkedIn. Write a unique caption for each platform. Plan one post per platform at 7 PM Europe/London each day, starting tomorrow. Keep all posts in one group. Show me the exact accounts, captions, dates and times for approval before creating or scheduling anything.
Review the exact selected accounts, captions, dates, and timezone. You can ask Muse Code to rewrite a caption or shift the schedule before approving the corresponding PostDovo tool action.
More Things to Ask Muse Code
- “Which social accounts do I have connected in PostDovo?”
- “Write a LinkedIn post about our updated opening hours and save it as a draft.”
- “Prepare three Facebook posts for tomorrow morning, lunch and evening. Show the times for approval before scheduling.”
- “Which posts are scheduled for this week? Show me Friday’s posts before unscheduling any.”
What Can Muse Code Manage Through PostDovo?
Muse Code can use the PostDovo MCP tools made available to its authorized workspace.
| Capability | What it lets you do |
|---|---|
| Connected accounts | View available social accounts and workspaces |
| Drafts | Create, edit and delete supported drafts |
| Platform-specific content | Customize captions for different destinations |
| Images and videos | Attach supported media to drafts |
| Schedules | Schedule posts or unschedule supported entries |
| Immediate publishing | Publish after the required preview and explicit approval |
| Post information | Review supported posts and publishing status |
Single Post vs. Generate Campaign
The MCP tools here support PostDovo’s Single Post workflow—one post can target multiple connected accounts, and groups of posts can be planned across dates. Generate Campaign is a separate feature that generates multi-day content from a website or topic.
Video and image publishing depends on successfully attaching compatible media. Local files are not automatically uploaded just because the agent can read them.
Supported Social Media Platforms
PostDovo offers 19 social media connection options. Compatible content can be created, scheduled and published through supported PostDovo tools. Platform-specific format restrictions apply.
| Social Media Platform | Create Content | Schedule Posts | Publish Posts |
|---|---|---|---|
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| Discord | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ |
* X (Twitter): Publishing posts, including scheduled posts, requires credits. Other platforms have their own format and authorization requirements.
Connect Accounts in PostDovo First
Open PostDovo, navigate to Connect Accounts, and authorize the social profiles you want Muse Code to use. The MCP connection doesn’t automatically connect Facebook or Instagram for you.
Is Muse Code Social Media Scheduling Free?
PostDovo’s Starter plan is $0/month and includes supported AI-agent connectivity. Meta’s model or Muse Code access may have separate subscription or API usage requirements.
| Starter feature | Included |
|---|---|
| Connected social accounts | Up to 5 |
| Workspaces | 1 |
| Single Post creation | Unlimited |
| Single Post scheduling | Unlimited |
| Single Post publishing | Unlimited except X credit requirements |
| Supported AI-agent connections | Included |
AI content-generation features may use separate PostDovo credits; X publishing uses credits.
Using Meta’s personal agent instead? Follow the Muse setup.
Common Muse Code MCP Problems
1. Muse command not found
Check muse --version. If not found, rerun Meta’s installer and open a new terminal so its PATH changes take effect.
2. Settings file fails to load
Check that ~/.config/muse/settings.json is valid JSON and includes "schema_version": 1. Avoid trailing commas and preserve other existing settings. A malformed settings file can prevent startup.
3. My Muse Code build uses mcpServers, not mcp_servers
Meta’s newer developer documentation calls mcpServers the preferred key and accepts the older mcp_servers format for compatibility. Use one format, not both in the same file. The equivalent newer-format configuration is below:
{
"schema_version": 1,
"mcpServers": {
"postdovo": {
"type": "streamable-http",
"url": "https://app.postdovo.com/mcp",
"required": false
}
}
}4. PostDovo shows as unavailable
Confirm the endpoint is https://app.postdovo.com/mcp. mode: optional lets Muse Code continue with a warning; it doesn’t mean the server is connected. Retry muse mcp login postdovo if OAuth is needed.
5. Browser sign-in doesn’t open
Check muse mcp login --help for options offered by your version, including headless authentication. Don’t confuse PostDovo’s OAuth login with Muse Code’s separate Meta model login.
6. Token authentication fails
Make sure POSTDOVO_TOKEN is available in the terminal that launches Muse Code and that the token has not expired or been revoked. Restart Muse Code after changing settings. You can switch to OAuth if preferred.
7. Connected accounts or scheduled posts are missing
Verify the active PostDovo workspace and that accounts are connected under Connect Accounts. Ask the agent to list accounts first; if a write action fails, inspect the actual tool error before retrying.
Muse Code + PostDovo FAQs
1. Can Muse Code schedule Facebook and LinkedIn posts?
Yes, when the relevant accounts are connected in PostDovo and Muse Code has successfully authenticated and invoked the supported PostDovo scheduling tools.
2. Is Muse Code the same as Meta Muse?
No. Muse Code is Meta’s terminal coding agent with documented MCP server settings. The regular Muse personal agent uses a different connector workflow.
3. Do I need a PostDovo access token?
Not for the browser OAuth flow using muse mcp login postdovo. An access token is an optional alternative for headless or other compatible setups.
4. Does Muse Code ask before publishing?
Muse Code uses a tool approval system depending on the tool and current permission settings. PostDovo requires explicit preview and approval for immediate publishing. Once approved, scheduled posts can publish automatically at their scheduled times.
5. Is PostDovo free for Muse Code users?
PostDovo Starter costs $0/month, including up to five connected social accounts and unlimited Single Post scheduling. Meta model access and X publishing may have separate charges.
6. How do I disconnect Muse Code from PostDovo?
Run muse mcp logout postdovo to end the Muse Code OAuth session. For token authentication, revoke the token in PostDovo and clear it from your environment. Remove the PostDovo server entry from settings if you no longer need it.
Try Social Media Scheduling from Muse Code
Connect your PostDovo workspace, confirm your social accounts, and use the three-day prompt to prepare a publishing plan. Review the content and times before approving scheduling.
PostDovo Starter: $0/month · Up to 5 social accounts · Unlimited Single Post scheduling.