GoHumanize Open Humanizer vs Any Chat Completions MCP
A side-by-side look at the GoHumanize Open Humanizer and Any Chat Completions MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GoHumanize Open Humanizer for conversational ai work as a local process; choose Any Chat Completions MCP for conversational ai over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GoHumanize Open Humanizer when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPEN_HUMANIZER_URL, OPEN_HUMANIZER_MODEL, OPEN_HUMANIZER_API_KEY, OPEN_HUMANIZER_SAMPLES.
Choose Any Chat Completions MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
AI_CHAT_KEY, AI_CHAT_NAME, AI_CHAT_MODEL, AI_CHAT_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | OPEN_HUMANIZER_URLOPEN_HUMANIZER_MODELOPEN_HUMANIZER_API_KEYOPEN_HUMANIZER_SAMPLES | AI_CHAT_KEYAI_CHAT_NAMEAI_CHAT_MODELAI_CHAT_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 165 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GoHumanize Open Humanizer | View Any Chat Completions MCP |
Tools & capabilities
GoHumanize Open Humanizer tools
No tool names declared yet. Check the project README from the listing page.
Any Chat Completions MCP 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.
GoHumanize Open Humanizer
{
"mcpServers": {
"gohumanize-open-humanizer": {
"command": "npx",
"args": [
"-y",
"gohumanize-open-humanizer-mcp"
],
"env": {
"OPEN_HUMANIZER_URL": "YOUR_OPEN_HUMANIZER_URL_HERE",
"OPEN_HUMANIZER_MODEL": "YOUR_OPEN_HUMANIZER_MODEL_HERE",
"OPEN_HUMANIZER_API_KEY": "YOUR_OPEN_HUMANIZER_API_KEY_HERE",
"OPEN_HUMANIZER_SAMPLES": "YOUR_OPEN_HUMANIZER_SAMPLES_HERE"
}
}
}
}
Any Chat Completions MCP
{
"mcpServers": {
"pyroprompts-any-chat-completions-mcp": {
"command": "uvx",
"args": [
"pyroprompts-any-chat-completions-mcp"
],
"env": {
"AI_CHAT_KEY": "YOUR_AI_CHAT_KEY_HERE",
"AI_CHAT_NAME": "YOUR_AI_CHAT_NAME_HERE",
"AI_CHAT_MODEL": "YOUR_AI_CHAT_MODEL_HERE",
"AI_CHAT_BASE_URL": "YOUR_AI_CHAT_BASE_URL_HERE"
}
}
}
}