CarryFeed vs Markaestro

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

CarryFeed logoCarryFeedSocial Media · Local subprocess (stdio)Resolve public X/Twitter profiles, posts, and media through CarryFeed.36FairAuth: not declaredMarkaestro logoMarkaestroSocial Media · Local subprocess (stdio)Schedule, publish, and review social posts and analytics for a Markaestro brand.43FairAuth: not declared

Verdict: choose CarryFeed for social media work as a local process; choose Markaestro 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?

CarryFeed logoChoose CarryFeed when

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCarryFeed logoCarryFeedMarkaestro logoMarkaestro
CategorySocial MediaSocial Media
Quality signal36/100 · Fair43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedMARKAESTRO_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

CarryFeed tools

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

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

CarryFeed

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "carryfeed": {
      "command": "npx",
      "args": [
        "-y",
        "@carryfeed/cli"
      ]
    }
  }
}

Markaestro

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "markaestro": {
      "command": "npx",
      "args": [
        "-y",
        "@markaestro/mcp"
      ],
      "env": {
        "MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

CarryFeed is categorized under Social Media and uses a local stdio subprocess. Markaestro belongs to Social Media and uses a local stdio subprocess. Pick CarryFeed for social media work and Markaestro 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.

CarryFeed has no declared pricing — check the project's own site. Markaestro 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 carryfeed and markaestro as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CarryFeed has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Markaestro has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.