Bottally vs Humanify MCP
A side-by-side look at the Bottally and Humanify MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BottallyMarketing · Remote HTTP/SSEAI marketing agent that writes and publishes a researched SEO article to your blog daily, builds backlinks and tracks if ChatGPT and Google AI cite you.43FairAuth: not declaredVerdict: choose Bottally for marketing work over a hosted endpoint; choose Humanify MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Bottally when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Humanify MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HUMANIFY_API_KEY. - You want tools like
humanify_transform.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Bottally | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 43/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | HUMANIFY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Bottally | View Humanify MCP |
Tools & capabilities
Bottally tools
No tool names declared yet. Check the project README from the listing page.
Humanify MCP tools 1
humanify_transformTransform AI-generated marketing copy into human-sounding, GEO-optimised content that gets cited by AI search engines. Returns transformed copy, a human-readability score (0-100), and a list of improvements made.
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.
Bottally
{
"mcpServers": {
"bottally": {
"command": "npx",
"args": [
"-y",
"bottally"
]
}
}
}
Humanify MCP
{
"mcpServers": {
"humanify-mcp": {
"command": "npx",
"args": [
"-y",
"@morebetterclaw/humanify-mcp"
],
"env": {
"HUMANIFY_API_KEY": "YOUR_HUMANIFY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Bottally is categorized under Marketing and uses a remote HTTP/SSE transport. Humanify MCP belongs to Marketing and uses a local stdio subprocess. Pick Bottally for marketing work and Humanify MCP for marketing.
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.
Bottally is listed as freemium — a free tier with paid plans. Humanify 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 bottally and humanify-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bottally has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Humanify MCP has 52/100 (Good) with 2 views, 0 installs and 0 GitHub stars.