Markaestro vs Schedulin
A side-by-side look at the Markaestro and Schedulin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SchedulinSocial Media · Remote HTTP/SSESchedule, publish, and analyze social posts across TikTok, Instagram, YouTube, X, LinkedIn + 5 more.44FairAuth: oauth 2.0Verdict: choose Markaestro for social media work as a local process; choose Schedulin for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Markaestro when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MARKAESTRO_API_KEY.
SChoose Schedulin when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Schedulin | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 43/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | MARKAESTRO_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Markaestro | View Schedulin |
Tools & capabilities
Markaestro tools
No tool names declared yet. Check the project README from the listing page.
Schedulin tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Markaestro
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}
Schedulin
{
"mcpServers": {
"schedulin": {
"url": "https://www.schedulin.app/mcp"
}
}
}
Frequently asked questions
Markaestro is categorized under Social Media and uses a local stdio subprocess. Schedulin belongs to Social Media and uses a remote HTTP/SSE transport. Pick Markaestro for social media work and Schedulin for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Markaestro has no declared pricing — check the project's own site. Schedulin has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add markaestro and schedulin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markaestro has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Schedulin has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.