ERIUS PHONE vs Avo
A side-by-side look at the ERIUS PHONE and Avo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ERIUS PHONE for developer tools work as a local process; choose Avo for data platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ERIUS PHONE when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ERIUS_PHONE_API_KEY, ERIUS_PHONE_DEFAULT_DEVICE, ERIUS_PHONE_API_URL, ERIUS_PHONE_TIMEOUT.
Choose Avo when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Data Platforms |
| Quality signal | 36/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | ERIUS_PHONE_API_KEYERIUS_PHONE_DEFAULT_DEVICEERIUS_PHONE_API_URLERIUS_PHONE_TIMEOUT | None listed |
Tools & capabilities
ERIUS PHONE tools
No tool names declared yet. Check the project README from the listing page.
Avo 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.
ERIUS PHONE
{
"mcpServers": {
"erius-phone": {
"command": "uvx",
"args": [
"erius-phone-mcp"
],
"env": {
"ERIUS_PHONE_API_KEY": "YOUR_ERIUS_PHONE_API_KEY_HERE",
"ERIUS_PHONE_DEFAULT_DEVICE": "YOUR_ERIUS_PHONE_DEFAULT_DEVICE_HERE",
"ERIUS_PHONE_API_URL": "YOUR_ERIUS_PHONE_API_URL_HERE",
"ERIUS_PHONE_TIMEOUT": "YOUR_ERIUS_PHONE_TIMEOUT_HERE"
}
}
}
}
Avo
{
"mcpServers": {
"avo": {
"url": "https://mcp.avo.app/mcp"
}
}
}
Frequently asked questions
ERIUS PHONE is categorized under Developer Tools and uses a local stdio subprocess. Avo belongs to Data Platforms and uses a remote HTTP/SSE transport. Pick ERIUS PHONE for developer tools work and Avo for data platforms.
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.
ERIUS PHONE has no declared pricing — check the project's own site. Avo has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 erius-phone and avo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ERIUS PHONE has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Avo has 44/100 (Fair) with 64 views, 0 installs and 1 GitHub stars.
