Pulse MCP vs Markaestro

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

Pulse MCP logoPulse MCPSocial Media · Local subprocess (stdio)Free, agent-first social-post metrics — a post URL in, views/likes/comments out.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 Pulse MCP 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?

Pulse MCP logoChoose Pulse MCP when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PULSE_API_URL.
  • You want tools like metrics, metrics_batch, history.
Explore Pulse MCP

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.

SpecPulse MCP logoPulse MCPMarkaestro 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 varsPULSE_API_URLMARKAESTRO_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars10
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools5Not listed

Tools & capabilities

Pulse MCP tools 5

  • metrics{ platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail }
  • metrics_batchthe same, one per URL (partial failures don't fail the batch)
  • historythe recorded growth curve — `{ count, points }` (posts: `{ t, views, likes, comments }`, profiles: `{ t, followers, posts }`), a snapshot per fresh fetch
  • profileaccount-level metrics — `{ handle, name, followers, following, posts, verified, avatar }` (YouTube, TikTok, Instagram, X, Bluesky, Mastodon)
  • profile_batchsame as `profile`, one per URL — order preserved; partial failures don't fail the batch. Compare follower counts across a list of creators.

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.

Pulse MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pulse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pulse-mcp"
      ],
      "env": {
        "PULSE_API_URL": "YOUR_PULSE_API_URL_HERE"
      }
    }
  }
}

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

Pulse MCP is categorized under Social Media and uses a local stdio subprocess. Markaestro belongs to Social Media and uses a local stdio subprocess. Pick Pulse MCP 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.

Pulse MCP 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 pulse-mcp and markaestro as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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