Markaestro vs Agent
A side-by-side look at the Markaestro and Agent 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 Agent 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 Agent when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TAISLY_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 43/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | MARKAESTRO_API_KEY | TAISLY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 220 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Markaestro | View Agent |
Tools & capabilities
Markaestro tools
No tool names declared yet. Check the project README from the listing page.
Agent 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": {
"markaestro": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "YOUR_MARKAESTRO_API_KEY_HERE"
}
}
}
}
Agent
{
"mcpServers": {
"taisly-agent": {
"command": "npx",
"args": [
"-y",
"@taisly/agent"
],
"env": {
"TAISLY_API_KEY": "YOUR_TAISLY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Markaestro is categorized under Social Media and uses a local stdio subprocess. Agent belongs to Social Media and uses a local stdio subprocess. Pick Markaestro for social media work and Agent 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. Agent is listed as freemium — a free tier with paid plans. Auth: api key required. 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 taisly-agent 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. Agent has 61/100 (Good) with 3 views, 0 installs and 220 GitHub stars.