Chatpipe MCP vs Vexa
A side-by-side look at the Chatpipe MCP and Vexa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chatpipe MCP for communication work over a hosted endpoint; choose Vexa for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chatpipe MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
publish_page, list_projects, update_page.
Choose Vexa when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | API_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,906 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Chatpipe MCP | View Vexa |
Tools & capabilities
Chatpipe MCP tools 4
publish_pagePublish HTML content as a live, shareable page. Returns a public URL.list_projectsList all published pages with their URLs, names, and access levels. Takes no parameters.update_pageUpdate the HTML content of an existing page. The URL remains the same.delete_pagePermanently remove a published page.
Vexa 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.
Chatpipe MCP
{
"mcpServers": {
"darktw-chatpipe-mcp": {
"url": "https://api.chatpipe.net/mcp"
}
}
}
Vexa
{
"mcpServers": {
"vexa": {
"url": "https://api.cloud.vexa.ai/bots"
}
}
}
Frequently asked questions
Chatpipe MCP is categorized under Communication and uses a remote HTTP/SSE transport. Vexa belongs to Communication and uses a remote HTTP/SSE transport. Pick Chatpipe MCP for communication work and Vexa for communication.
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.
Chatpipe MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Vexa 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 darktw-chatpipe-mcp and vexa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpipe MCP has a quality signal of 52/100 (Good) with 5 views, 0 installs and 1 GitHub stars. Vexa has 48/100 (Fair) with 2 views, 0 installs and 2,906 GitHub stars.