Markaestro vs Openshorts

A side-by-side look at the Markaestro and Openshorts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Markaestro logoMarkaestroSocial Media · Local subprocess (stdio)Schedule, publish, and review social posts and analytics for a Markaestro brand.43FairAuth: not declaredOpenshorts logoOpenshortsSocial Media · Local subprocess (stdio)Turn long videos into viral vertical shorts and publish them to TikTok, Instagram and YouTube.48FairAuth: not declared

Verdict: choose Markaestro for social media work as a local process; choose Openshorts for social media as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Markaestro logoChoose 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.
Explore Markaestro

Openshorts logoChoose Openshorts when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
Explore Openshorts

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMarkaestro logoMarkaestroOpenshorts logoOpenshorts
CategorySocial MediaSocial Media
Quality signal43/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMARKAESTRO_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars07,047
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Markaestro tools

No tool names declared yet. Check the project README from the listing page.

Openshorts 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "markaestro": {
      "command": "npx",
      "args": [
        "-y",
        "@markaestro/mcp"
      ],
      "env": {
        "MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
      }
    }
  }
}

Openshorts

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openshorts": {
      "command": "uvx",
      "args": [
        "openshorts"
      ]
    }
  }
}

Frequently asked questions

Markaestro is categorized under Social Media and uses a local stdio subprocess. Openshorts belongs to Social Media and uses a local stdio subprocess. Pick Markaestro for social media work and Openshorts 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. Openshorts has no declared pricing — check the project's own site. 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 openshorts 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. Openshorts has 48/100 (Fair) with 2 views, 0 installs and 7,047 GitHub stars.