Markaestro vs Pulse MCP
A side-by-side look at the Markaestro and Pulse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Markaestro for social media work as a local process; choose Pulse MCP 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?
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.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 43/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MARKAESTRO_API_KEY | PULSE_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Markaestro | View Pulse MCP |
Tools & capabilities
Markaestro tools
No tool names declared yet. Check the project README from the listing page.
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 fetchprofileaccount-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.
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"
}
}
}
}
Pulse MCP
{
"mcpServers": {
"pulse-mcp": {
"command": "npx",
"args": [
"-y",
"pulse-mcp"
],
"env": {
"PULSE_API_URL": "YOUR_PULSE_API_URL_HERE"
}
}
}
}
Frequently asked questions
Markaestro is categorized under Social Media and uses a local stdio subprocess. Pulse MCP belongs to Social Media and uses a local stdio subprocess. Pick Markaestro for social media work and Pulse MCP 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. Pulse MCP 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 pulse-mcp 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. Pulse MCP has 36/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.