Markaestro vs Zevari

A side-by-side look at the Markaestro and Zevari 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 declared
Z
ZevariSocial Media
Controlled LinkedIn and GTM MCP server with review-gated prospecting and outreach workflows.37FairAuth: not declared

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

Z
Choose Zevari when

  • You need dedicated capabilities in the Social Media domain.
Explore Zevari

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMarkaestro logoMarkaestro
Z
Zevari
CategorySocial MediaSocial Media
Quality signal43/100 · Fair37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMARKAESTRO_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0—
Directory activity 1 views 0 installs 0 upvotes 0 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.

Zevari 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"
      }
    }
  }
}

Zevari

No confirmed install command for Zevari yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Markaestro is categorized under Social Media and uses a local stdio subprocess. Zevari belongs to Social Media and uses an install path we have not confirmed yet. Pick Markaestro for social media work and Zevari 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. Zevari has no confirmed install command yet — follow its own setup instructions.

Markaestro has no declared pricing — check the project's own site. Zevari 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 zevari 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. Zevari has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.